From: Richard Guy Briggs <rgb@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
peterz@infradead.org, paulmck@linux.vnet.ibm.com,
laijs@cn.fujitsu.com, akpm@linux-foundation.org, joe@perches.com,
keescook@chromium.org, geert@linux-m68k.org, jkosina@suse.cz,
viro@zeniv.linux.org.uk, davem@davemloft.net,
linux-kernel@vger.kernel.org, mingo@elte.hu, rostedt@goodmis.org,
tglx@linutronix.de, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Change task_struct->comm to use RCU.
Date: Mon, 24 Mar 2014 11:43:48 -0400 [thread overview]
Message-ID: <20140324154348.GA20004@madcap2.tricolour.ca> (raw)
In-Reply-To: <alpine.LRH.2.02.1403120052040.23883@tundra.namei.org>
On 14/03/12, James Morris wrote:
> On Tue, 11 Mar 2014, Tetsuo Handa wrote:
> > And the same phrase goes to James Morris...
> >
> > If you are sure that it is safe to use get_task_comm() from
> > dump_common_audit_data() and you prefer locked version, please pick up below
> > patch via your git tree.
> >
> > If you are unsure or prefer lockless version, I'll make a lockless version
> > using do_get_task_comm() proposed in this thread.
>
> If you can't understand whether your patch is correct or not, don't ask me
> to apply it to my tree.
>
> If you're unsure, get it reviewed first.
I looked at the calling function tree back a number of steps and didn't
see any other evidence of task locks held, so I'm comfortable with this
patch and would prefer it to either memcpy() or do_get_task_comm(), but
would still like to get an opinion from others.
> - James
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2014-03-24 15:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201402072303.DJD13007.JFFMSLHOOFQOtV@I-love.SAKURA.ne.jp>
[not found] ` <20140207140536.943daf965008b9428cdcb468@linux-foundation.org>
[not found] ` <201402081055.BGJ73403.tQMLFVOJSOOFFH@I-love.SAKURA.ne.jp>
[not found] ` <20140207180647.5944fe3d.akpm@linux-foundation.org>
[not found] ` <201402092327.JAD12489.QOLSFVMHJtFOOF@I-love.SAKURA.ne.jp>
2014-02-10 13:43 ` [PATCH (draft)] " Tetsuo Handa
2014-02-17 11:27 ` [PATCH] " Tetsuo Handa
2014-02-24 23:51 ` Paul E. McKenney
2014-02-26 13:44 ` Tetsuo Handa
2014-02-26 15:26 ` Paul E. McKenney
2014-02-25 1:49 ` Lai Jiangshan
2014-02-25 10:05 ` Peter Zijlstra
2014-02-25 12:54 ` Tetsuo Handa
2014-02-25 14:46 ` Peter Zijlstra
2014-03-07 12:20 ` Tetsuo Handa
2014-03-07 15:54 ` Richard Guy Briggs
2014-03-08 12:43 ` Tetsuo Handa
2014-03-10 20:21 ` Richard Guy Briggs
2014-03-11 12:02 ` Tetsuo Handa
2014-03-11 12:16 ` Tetsuo Handa
2014-03-11 13:55 ` James Morris
2014-03-24 15:43 ` Richard Guy Briggs [this message]
2014-03-27 17:20 ` [PATCH] LSM: Pass comm name via get_task_comm() [was: Re: [PATCH] Change task_struct->comm to use RCU.] Richard Guy Briggs
2014-03-27 18:06 ` Stephen Smalley
2014-09-19 3:30 ` Richard Guy Briggs
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=20140324154348.GA20004@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jkosina@suse.cz \
--cc=jmorris@namei.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome