Messages in this thread | | | Date | Sat, 12 Jan 2013 19:12:58 +0100 | From | Oleg Nesterov <> | Subject | Re: PTRACE_SYSCALL && vsyscall (Was: arch_check_bp_in_kernelspace: fix the range check) |
| |
On 01/10, u3557@miso.sublimeip.com wrote: > > Hi Everyone, > > > On 01/08, Pedro Alves wrote: > >> > >> On 12/04/2012 05:59 PM, Oleg Nesterov wrote: > >> > >> > But If we want to allow to trace vsyscall's, hw bp doesn't look very > >> > nice imo. HBP_NUM = 4 and you need to setup 3 bp's to trace them all. > >> > >> Irrespective of the whole syscall tracing issue, allowing HW bkpts in > >> the vsyscall just seems like a bug fix to me. > > > > And I never argued. I sent the patch iirc ;) > > Exactly, it is a bug and I am still waiting for it to be fixed in the > Linux kernel.
I would not say this is a bug but let me repeat, no need to convince me.
Please feel free to re-send the patch(es) I sent to maintainers. Sorry, I can't push these changes into Linus's tree.
Oleg.
| |