Revision d4565649b6d6923369112758212b851adc407f0c authored by Al Viro on 28 February 2016, 00:23:16 UTC, committed by Al Viro on 28 February 2016, 00:23:16 UTC
both do_last() and walk_component() risk picking a NULL inode out of dentry about to become positive, *then* checking its flags and seeing that it's not negative anymore and using (already stale by then) value they'd fetched earlier. Usually ends up oopsing soon after that... Cc: stable@vger.kernel.org # v3.13+ Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
1 parent c80567c
| File | Mode | Size |
|---|---|---|
| apparmor | ||
| integrity | ||
| keys | ||
| selinux | ||
| smack | ||
| tomoyo | ||
| yama | ||
| Kconfig | -rw-r--r-- | 5.6 KB |
| Makefile | -rw-r--r-- | 900 bytes |
| commoncap.c | -rw-r--r-- | 31.3 KB |
| device_cgroup.c | -rw-r--r-- | 21.0 KB |
| inode.c | -rw-r--r-- | 6.5 KB |
| lsm_audit.c | -rw-r--r-- | 9.9 KB |
| min_addr.c | -rw-r--r-- | 1.3 KB |
| security.c | -rw-r--r-- | 53.3 KB |
Computing file changes ...
