* Jan Beulich <[email protected]> wrote:
> validating that the item read is between current and previous stack
> pointer, which in turn are being derived from register state and
> unwind information.
i still dont quite get it - and i feel deja vu. Didnt we agree that the
right way to go about this is to validate all stack information based on
what the kernel already knows about all the stacks that the task may
use? I.e. only allow pointers into the kernel stack and into the various
kernel stacks. No 'probe kernel pointer' or anything. If the unwind data
or register state ever points outside that basic filter, abandon the
walk. Am i missing something?
Ingo
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
