From: Ingo Molnar Subject: Re: [PATCH 3/4] signals/sigaltstack: Report current flag bits in sigaltstack() Date: Wed, 4 May 2016 08:33:57 +0200 Message-ID: <20160504063357.GA12846@gmail.com> References: <94b291ec9fd47741a9264851e316e158ded0b00d.1462296606.git.luto@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <94b291ec9fd47741a9264851e316e158ded0b00d.1462296606.git.luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andy Lutomirski Cc: x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Borislav Petkov , Stas Sergeev , Al Viro , Amanieu d'Antras , Andrew Morton , Andy Lutomirski , Brian Gerst , Denys Vlasenko , "H. Peter Anvin" , Linus Torvalds , Michal Hocko , Oleg Nesterov , Pavel Emelyanov , "Peter Zijlstra (Intel)" , Richard Weinberger , Sasha Levin , Shuah Khan , Thomas Gleixner , Vladimir Davydov , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-api@vger.kernel.org * Andy Lutomirski wrote: > sigaltstack()'s reported previous state uses a somewhat odd > convention, but the concept of flag bits is new, and we can do the > flag bits sensibly. Specifically, let's just report them directly. > > This will allow saving and restoring the sigaltstack state using > sigaltstack() to work correctly. > > Signed-off-by: Stas Sergeev This SOB seems stray as well, so I've removed it too. Thanks, Ingo