From: Davidlohr Bueso <davidlohr@hp.com>
To: Mathias Krause <minipli@googlemail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
PaX Team <pageexec@freemail.hu>,
Nadia Derbey <Nadia.Derbey@bull.net>,
Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [PATCH] ipc: constify ipc_ops
Date: Mon, 31 Mar 2014 07:12:36 -0700 [thread overview]
Message-ID: <1396275156.2507.4.camel@buesod1.americas.hpqcorp.net> (raw)
In-Reply-To: <CA+rthh93hc5w_yKMLyJmEZFrW0NbHU3TEf_YL4cpE5OT3hvpLQ@mail.gmail.com>
On Mon, 2014-03-31 at 10:28 +0200, Mathias Krause wrote:
> On 30 March 2014 23:47, Davidlohr Bueso <davidlohr@hp.com> wrote:
> > On Sun, 2014-03-30 at 15:35 +0200, Mathias Krause wrote:
> >> There is no need to recreate the very same ipc_ops structure on every
> >> kernel entry for msgget/semget/shmget. Just declare it static and be
> >> done with it.
> >> While at it, constify it as we don't modify the structure at runtime.
> >
> > Seems reasonable.
> >
> >>
> >> Found in the PaX patch, written by the PaX Team.
> >>
> >> Cc: PaX Team <pageexec@freemail.hu>
> >> Cc: Nadia Derbey <Nadia.Derbey@bull.net>
> >> Cc: Andrew Morton <akpm@linux-foundation.org>
> >> Signed-off-by: Mathias Krause <minipli@googlemail.com>
> >
> > In the future, for ipc changes, please CC me and Manfred as well.
>
> As there is no maintainer entry for ipc/ in the MAINTAINERS file I
> looked at the recent commit history of ipc/ and found that most of the
> patches went in via Andrew and then Linus. But it's true, you and
> Manfred have quite some patches in the recent past. Though, having an
> official maintaner for ipc/ would accelerate the gyrating phase of
> whom to send the patches to in the future. Are you volunteering? :)
>
> >
> > One comment below, otherwise:
> > Acked-by: Davidlohr Bueso <davidlohr@hp.com>
> >
> >> ---
> >> ipc/msg.c | 9 ++++-----
> >> ipc/sem.c | 10 +++++-----
> >> ipc/shm.c | 10 +++++-----
> >> ipc/util.c | 8 ++++----
> >> ipc/util.h | 2 +-
> >> 5 files changed, 19 insertions(+), 20 deletions(-)
> >>
> >> diff --git a/ipc/msg.c b/ipc/msg.c
> >> index 649853105a..35e4018de5 100644
> >> --- a/ipc/msg.c
> >> +++ b/ipc/msg.c
> >> @@ -306,15 +306,14 @@ static inline int msg_security(struct kern_ipc_perm *ipcp, int msgflg)
> >> SYSCALL_DEFINE2(msgget, key_t, key, int, msgflg)
> >> {
> >> struct ipc_namespace *ns;
> >> - struct ipc_ops msg_ops;
> >> + static const struct ipc_ops msg_ops = {
> >> + .getnew = newque,
> >> + .associate = msg_security,
> >
> > For completeness, please add .more_checks = NULL as well.
>
> The C standard already ensures that .more_checks is initialized with
> NULL. So I don't see any benefit from doing it explicitly.
> We're not initializing global/static variables holding NULL pointers
> in the majority of the code base either, so this is just "best
> practice".
Hence the word _completeness_.
next prev parent reply other threads:[~2014-03-31 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 13:35 Mathias Krause
2014-03-30 21:47 ` Davidlohr Bueso
2014-03-31 8:28 ` Mathias Krause
2014-03-31 14:12 ` Davidlohr Bueso [this message]
2014-03-31 21:59 ` Andrew Morton
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=1396275156.2507.4.camel@buesod1.americas.hpqcorp.net \
--to=davidlohr@hp.com \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=minipli@googlemail.com \
--cc=pageexec@freemail.hu \
/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®