Q: a bogus set_fs(USER_DS) in setup_frame/setup_rt_frame ?

I am really puzzled by set_fs(USER_DS) in setup_frame/setup_rt_frame.

How is it possible that current->addr_limit != USER_DS ? If this _is_
possible, how can can we trust the result of access_ok() above?

Thanks in advance,

Oleg.

-
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/

---

• Follow-Ups:
  • Re: Q: a bogus set_fs(USER_DS) in setup_frame/setup_rt_frame ?
    • From: Linus Torvalds <[email protected]>
  • [patch] i386: remove unnecessary code
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: Hibernation considerations
• Next by Date: Re: [PATCH] ACPI: Add reboot mechanism
• Previous by thread: [RFC/T PATCH 00/12] lockdep: annotate lock_page
• Next by thread: [patch] i386: remove unnecessary code
• Index(es):
  • Date
  • Thread

[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]