diff options
| author | John Johansen <john.johansen@canonical.com> | 2012-05-16 11:01:05 -0700 |
|---|---|---|
| committer | John Johansen <john.johansen@canonical.com> | 2012-05-18 11:09:52 -0700 |
| commit | cffee16e8b997ab947de661e8820e486b0830c94 (patch) | |
| tree | f71adb789f6d850367d35b34955f038239f739b3 /security/tomoyo | |
| parent | bf83208e0b7f5938f5a7f6d9dfa9960bf04692fa (diff) | |
apparmor: fix long path failure due to disconnected path
BugLink: http://bugs.launchpad.net/bugs/955892
All failures from __d_path where being treated as disconnected paths,
however __d_path can also fail when the generated pathname is too long.
The initial ENAMETOOLONG error was being lost, and ENAMETOOLONG was only
returned if the subsequent dentry_path call resulted in that error. Other
wise if the path was split across a mount point such that the dentry_path
fit within the buffer when the __d_path did not the failure was treated
as a disconnected path.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Diffstat (limited to 'security/tomoyo')
0 files changed, 0 insertions, 0 deletions