From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Kees Cook <keescook@chromium.org>, Jann Horn <jannh@google.com>
Subject: Re: [PATCH] kernel/compat.c: mark expected switch fall-throughs
Date: Tue, 16 Apr 2019 18:53:27 +1000 [thread overview]
Message-ID: <20190416185327.5c129073@canb.auug.org.au> (raw)
In-Reply-To: <CAK8P3a31Cp_COwjuOm6uG_23M3Ys4tJTB33jBENj-so0jkhgzg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
Hi Arnd,
On Tue, 16 Apr 2019 10:32:55 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
Thanks
> It's a bit inconsistent though since put_compat_sigset() has the
> comments in separate lines, as of commit 89976005536c
> ("include/linux/compat.h: mark expected switch fall-throughs").
OK, I wasn't aware of that one.
> I don't care either way, but it might be better to do it the same way
> for both.
Indeed, I will redo it that way (with your Acked-by).
> We could also consider just getting rid of put_compat_sigset() and
> get_compat_sigset() but replacing them with a combined
> put_sigset()/get_sigset() that does the right thing for both native
> and compat tasks. This lets us kill a couple of compat system
> calls that only differ in their sigset_t argument. On little-endian
> systems (which are the vast majority of the installed base), there
> is no difference anyway there is no overhead anyway since
> native and compat sigset_t are identical.
That sounds like a bigger patch that would require some real testing :-)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-16 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 7:29 Stephen Rothwell
2019-04-16 8:32 ` Arnd Bergmann
2019-04-16 8:53 ` Stephen Rothwell [this message]
2019-04-16 9:14 ` Arnd Bergmann
2019-05-15 5:23 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190416185327.5c129073@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=gustavo@embeddedor.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®