On Mon, 25 Apr 2005, Roland McGrath wrote:
>
> What would you think about a general hack to let given fixup table entries
> say the code wants the trap and error info made available (pushed on the
> stack or whatever)?
Yes, that sounds fine, if there is just some sane way to indicate that
(normally the fixup eip is close to the faulting eip, so there should be
tons of bits available, but it would need to be something clean? For iret,
I guess we could just set fixup-eip to zero, which would mean "return to
eip+1 and set error", but that sounds pretty hacky too)
> Conversely, would there be any harm in always setting
> ->thread.error_code and ->thread.trap_no for a kernel trap?
Page-ins etc in kernel mode are normal, and they shouldn't set the thread
state. So I think the "turn it into a trap" thing is nicer.
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
