Messages in this thread | | | Date | Fri, 25 May 2018 00:30:41 +0200 | From | Christian Brauner <> | Subject | Re: [REVIEW][PATCH 1/6] vfs: Don't allow changing the link count of an inode with an invalid uid or gid |
| |
On Thu, May 24, 2018 at 07:58:32AM -0500, Seth Forshee wrote: > On Wed, May 23, 2018 at 06:25:33PM -0500, Eric W. Biederman wrote: > > Changing the link count of an inode via unlink or link will cause a > > write back of that inode. If the uids or gids are invalid (aka not known > > to the kernel) writing the inode back may change the uid or gid in the > > filesystem. To prevent possible filesystem and to avoid the need for > > filesystem maintainers to worry about it don't allow operations on > > inodes with an invalid uid or gid. > > > > Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> > > Acked-by: Seth Forshee <seth.forshee@canonical.com>
Acked-by: Christian Brauner <christian@brauner.io>
| |