Re: [PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-05 Thread Serge Hallyn
Quoting Seth Forshee (seth.fors...@canonical.com): > On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote: > > Quoting Seth Forshee (seth.fors...@canonical.com): > > > Filesystem uids which don't map into a user namespace may result > > > in inode->i_uid being INVALID_UID. A symlink and

Re: [PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-05 Thread Seth Forshee
On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote: > Quoting Seth Forshee (seth.fors...@canonical.com): > > Filesystem uids which don't map into a user namespace may result > > in inode->i_uid being INVALID_UID. A symlink and its parent > > could have different owners in the filesystem

Re: [PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-05 Thread Serge Hallyn
Quoting Seth Forshee (seth.fors...@canonical.com): > Filesystem uids which don't map into a user namespace may result > in inode->i_uid being INVALID_UID. A symlink and its parent > could have different owners in the filesystem can both get > mapped to INVALID_UID, which may result in following a

Re: [PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-05 Thread Serge Hallyn
Quoting Seth Forshee (seth.fors...@canonical.com): Filesystem uids which don't map into a user namespace may result in inode-i_uid being INVALID_UID. A symlink and its parent could have different owners in the filesystem can both get mapped to INVALID_UID, which may result in following a

Re: [PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-05 Thread Seth Forshee
On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote: Quoting Seth Forshee (seth.fors...@canonical.com): Filesystem uids which don't map into a user namespace may result in inode-i_uid being INVALID_UID. A symlink and its parent could have different owners in the filesystem can both

Re: [PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-05 Thread Serge Hallyn
Quoting Seth Forshee (seth.fors...@canonical.com): On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote: Quoting Seth Forshee (seth.fors...@canonical.com): Filesystem uids which don't map into a user namespace may result in inode-i_uid being INVALID_UID. A symlink and its parent

[PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-02 Thread Seth Forshee
Filesystem uids which don't map into a user namespace may result in inode->i_uid being INVALID_UID. A symlink and its parent could have different owners in the filesystem can both get mapped to INVALID_UID, which may result in following a symlink when this would not have otherwise been permitted.

[PATCH v2 1/3] vfs: Check for invalid i_uid in may_follow_link()

2014-09-02 Thread Seth Forshee
Filesystem uids which don't map into a user namespace may result in inode-i_uid being INVALID_UID. A symlink and its parent could have different owners in the filesystem can both get mapped to INVALID_UID, which may result in following a symlink when this would not have otherwise been permitted.