From: Christoph Hellwig <hch@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: james_p_freyensee@linux.intel.com,
Christoph Hellwig <hch@infradead.org>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
suhail.ahmed@intel.com
Subject: Re: [PATCH 01/12] export kernel call get_task_comm()
Date: Tue, 8 Feb 2011 15:28:56 -0500 [thread overview]
Message-ID: <20110208202856.GA16696@infradead.org> (raw)
In-Reply-To: <20110208202852.160c080b@lxorguk.ukuu.org.uk>
On Tue, Feb 08, 2011 at 08:28:52PM +0000, Alan Cox wrote:
> On Tue, 8 Feb 2011 11:44:16 -0800 (PST)
> > > From current you can just dereference current->comm, and access from
> > > other threads from drivers is a bad idea.
>
> You need to take the locks for it - which get_task_comm encapsulates.
Not for current->comm, which is the only thing it cares about.
next prev parent reply other threads:[~2011-02-08 20:29 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 19:34 Resend: Request for review and addition of PTI implementation into kernel james_p_freyensee
2011-02-08 19:34 ` [PATCH 01/12] export kernel call get_task_comm() james_p_freyensee
2011-02-08 19:34 ` [PATCH 02/12] Kernel documentation for the PTI feature james_p_freyensee
2011-02-08 19:34 ` [PATCH 03/12] Intel PTI implementaiton of 1149 james_p_freyensee
2011-02-08 19:34 ` [PATCH 04/12] PTI Kconfig change in misc james_p_freyensee
2011-02-08 19:34 ` [PATCH 05/12] PTI misc Makefile addition james_p_freyensee
2011-02-08 19:34 ` [PATCH 06/12] PTI header file james_p_freyensee
2011-02-08 19:34 ` [PATCH 07/12] n_tracerouter and n_tracesink additions james_p_freyensee
2011-02-08 19:34 ` [PATCH 08/12] n_tracesink ldisc addition james_p_freyensee
2011-02-08 19:34 ` [PATCH 09/12] n_tracesink header file james_p_freyensee
2011-02-08 19:34 ` [PATCH 10/12] n_tracerouter ldisc driver james_p_freyensee
2011-02-08 19:34 ` [PATCH 11/12] n_tracerouter and n_tracesink Kconfig james_p_freyensee
2011-02-08 19:34 ` [PATCH 12/12] n_tracerouter and n_tracesink Makefile addition james_p_freyensee
2011-02-08 21:03 ` [PATCH 11/12] n_tracerouter and n_tracesink Kconfig Randy Dunlap
2011-02-17 19:23 ` [PATCH 09/12] n_tracesink header file Greg KH
2011-02-17 19:45 ` J Freyensee
2011-02-17 19:54 ` Greg KH
2011-02-17 20:10 ` J Freyensee
2011-02-17 21:43 ` Greg KH
2011-02-22 20:22 ` J Freyensee
2011-02-22 20:26 ` Greg KH
2011-02-22 22:55 ` J Freyensee
2011-02-17 19:21 ` [PATCH 07/12] n_tracerouter and n_tracesink additions Greg KH
2011-02-17 19:43 ` J Freyensee
2011-02-17 19:54 ` Greg KH
2011-02-17 20:11 ` J Freyensee
2011-02-24 11:52 ` Alan Cox
2011-02-17 19:20 ` [PATCH 06/12] PTI header file Greg KH
2011-02-17 19:41 ` J Freyensee
2011-02-17 19:55 ` Greg KH
2011-02-17 20:13 ` J Freyensee
2011-02-17 19:20 ` [PATCH 04/12] PTI Kconfig change in misc Greg KH
2011-02-17 19:35 ` J Freyensee
2011-02-17 19:45 ` Greg KH
2011-02-08 20:55 ` [PATCH 02/12] Kernel documentation for the PTI feature Randy Dunlap
2011-02-08 19:38 ` [PATCH 01/12] export kernel call get_task_comm() Christoph Hellwig
2011-02-08 19:44 ` james_p_freyensee
2011-02-08 20:04 ` Christoph Hellwig
2011-02-08 20:35 ` james_p_freyensee
2011-02-08 20:28 ` Alan Cox
2011-02-08 20:28 ` Christoph Hellwig [this message]
2011-02-08 20:36 ` Alan Cox
2011-02-15 10:57 ` Christoph Hellwig
2011-02-22 18:38 ` J Freyensee
2011-02-22 18:41 ` Greg KH
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=20110208202856.GA16696@infradead.org \
--to=hch@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=james_p_freyensee@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suhail.ahmed@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).