On Tue, 2 Aug 2005, Nick Piggin wrote:
>
> Surely this introduces integrity problems when `force` is not set?
"force" changes how we test the vma->vm_flags, that was always the
meaning from a security standpoint (and that hasn't changed).
The old code had this "lookup_write = write && !force;" thing because
there it used "force" to _clear_ the write bit test, and that was what
caused the race in the first place - next time around we would accept a
non-writable page, even if it hadn't actually gotten COW'ed.
So no, the patch doesn't introduce integrity problems by ignoring "force".
Quite the reverse - it _removes_ the integrity problems by ignoring it
there. That's kind of the whole point.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |