From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755750AbcECJ70 (ORCPT ); Tue, 3 May 2016 05:59:26 -0400 Received: from mail.skyhub.de ([78.46.96.112]:41500 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755500AbcECJ7W (ORCPT ); Tue, 3 May 2016 05:59:22 -0400 Date: Tue, 3 May 2016 11:59:12 +0200 From: Borislav Petkov To: Stas Sergeev Cc: linux-tip-commits@vger.kernel.org, sasha.levin@oracle.com, linux-kernel@vger.kernel.org, hpa@zytor.com, shuahkh@osg.samsung.com, xemul@parallels.com, luto@amacapital.net, mingo@kernel.org, vdavydov@parallels.com, torvalds@linux-foundation.org, amanieu@gmail.com, peterz@infradead.org, stsp@list.ru, viro@zeniv.linux.org.uk, tglx@linutronix.de, oleg@redhat.com, mhocko@suse.com, dvlasenk@redhat.com, akpm@linux-foundation.org, brgerst@gmail.com, richard@nod.at Subject: Re: [tip:core/signals] signals/sigaltstack: Prepare to add new SS_xxx flags Message-ID: <20160503095912.GD27540@pd.tnic> References: <1460665206-13646-3-git-send-email-stsp@list.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 03, 2016 at 12:50:06AM -0700, tip-bot for Stas Sergeev wrote: > Commit-ID: 407bc16ad1769f5cb8ad9555611cb198187ef4cd > Gitweb: http://git.kernel.org/tip/407bc16ad1769f5cb8ad9555611cb198187ef4cd > Author: Stas Sergeev > AuthorDate: Thu, 14 Apr 2016 23:20:03 +0300 > Committer: Ingo Molnar > CommitDate: Tue, 3 May 2016 08:37:59 +0200 > > signals/sigaltstack: Prepare to add new SS_xxx flags > > This patch adds SS_FLAG_BITS - the mask that splits sigaltstack > mode values and bit-flags. Since there is no bit-flags yet, the > mask is defined to 0. The flags are added by subsequent patches. > With every new flag, the mask should have the appropriate bit cleared. > > This makes sure if some flag is tried on a kernel that doesn't > support it, the -EINVAL error will be returned, because such a > flag will be treated as an invalid mode rather than the bit-flag. > > That way the existence of the particular features can be probed > at run-time. > > This change was suggested by Andy Lutomirski: > > https://lkml.org/lkml/2016/3/6/158 Please use the message ID in the future Message-ID: to refer to public mails because random web services caching lkml tend to become unreliable or even disappear at some point. I.e., see Link: format below for an example. > Signed-off-by: Stas Sergeev > Cc: Al Viro > Cc: Amanieu d'Antras > Cc: Andrew Morton > Cc: Andy Lutomirski > Cc: Borislav Petkov > Cc: Brian Gerst > Cc: Denys Vlasenko > Cc: H. Peter Anvin > Cc: Linus Torvalds > Cc: Michal Hocko > Cc: Oleg Nesterov > Cc: Pavel Emelyanov > Cc: Peter Zijlstra (Intel) > Cc: Peter Zijlstra > Cc: Richard Weinberger > Cc: Sasha Levin > Cc: Shuah Khan > Cc: Thomas Gleixner > Cc: Vladimir Davydov > Cc: linux-api@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Link: http://lkml.kernel.org/r/1460665206-13646-3-git-send-email-stsp@list.ru > Signed-off-by: Ingo Molnar > --- > include/uapi/linux/signal.h | 3 +++ > kernel/signal.c | 16 ++++++---------- > 2 files changed, 9 insertions(+), 10 deletions(-) Thanks. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.