|
Message-ID: <20120227180847.GA13264@redhat.com> Date: Mon, 27 Feb 2012 19:08:47 +0100 From: Oleg Nesterov <oleg@...hat.com> To: Roland McGrath <mcgrathr@...gle.com> Cc: Will Drewry <wad@...omium.org>, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, linux-doc@...r.kernel.org, kernel-hardening@...ts.openwall.com, netdev@...r.kernel.org, x86@...nel.org, arnd@...db.de, davem@...emloft.net, hpa@...or.com, mingo@...hat.com, peterz@...radead.org, rdunlap@...otime.net, tglx@...utronix.de, luto@....edu, eparis@...hat.com, serge.hallyn@...onical.com, djm@...drot.org, scarybeasts@...il.com, indan@....nu, pmoore@...hat.com, akpm@...ux-foundation.org, corbet@....net, eric.dumazet@...il.com, markus@...omium.org, coreyb@...ux.vnet.ibm.com, keescook@...omium.org Subject: Re: [PATCH v11 08/12] signal, x86: add SIGSYS info and make it synchronous. On 02/27, Roland McGrath wrote: > > On Mon, Feb 27, 2012 at 9:22 AM, Oleg Nesterov <oleg@...hat.com> wrote: > > SYNCHRONOUS_MASK just tells dequeue_signal() "pick them first". > > This is needed to make sure that the handler for, say SIGSEGV, > > can use ucontext->ip as a faulting addr. > > It's desireable to have these signals handled first just so that the thread > state that provoked the signal is not obscured by an unrelated asynchronous > signal having its handler setup done beforehand. OK, then probably it makes sense to update the changelog, "To ensure that SIGSYS delivery occurs on return from the triggering system call" looks confusing imho. Not that I really understand why "setup_rt_frame() first" really matters in this case, siginfo should carry all necessary info. IOW, may be "run this handler first" makes more sense but this change makes the opposite. OK, I won't argue, just I was confused by the changelog. Oleg.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.