From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>,
John Stultz <john.stultz@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 3/3] comm: ext4: Protect task->comm access by using get_task_comm()
Date: Wed, 4 May 2011 16:42:57 -0700 [thread overview]
Message-ID: <20110504164257.5bb61879.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110504163657.52dca3fc.akpm@linux-foundation.org>
Also. As direct access to current->comm is now verboten, we should add
a checkpatch rule to shout at people when they do it.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>,
John Stultz <john.stultz@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 3/3] comm: ext4: Protect task->comm access by using get_task_comm()
Date: Wed, 4 May 2011 16:42:57 -0700 [thread overview]
Message-ID: <20110504164257.5bb61879.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110504163657.52dca3fc.akpm@linux-foundation.org>
Also. As direct access to current->comm is now verboten, we should add
a checkpatch rule to shout at people when they do it.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-05-04 23:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 4:03 [RFC][PATCH 0/3] Improve task->comm locking situation John Stultz
2011-04-28 4:03 ` John Stultz
2011-04-28 4:03 ` [PATCH 1/3] comm: Introduce comm_lock seqlock to protect task->comm access John Stultz
2011-04-28 4:03 ` John Stultz
2011-04-28 4:03 ` [PATCH 2/3] comm: timerstats: Protect task->comm access by using get_task_comm() John Stultz
2011-04-28 4:03 ` John Stultz
2011-04-28 4:03 ` [PATCH 3/3] comm: ext4: " John Stultz
2011-04-28 4:03 ` John Stultz
2011-04-28 21:35 ` David Rientjes
2011-04-28 21:35 ` David Rientjes
2011-05-04 23:36 ` Andrew Morton
2011-05-04 23:36 ` Andrew Morton
2011-05-04 23:42 ` Andrew Morton [this message]
2011-05-04 23:42 ` Andrew Morton
2011-05-04 23:55 ` John Stultz
2011-05-04 23:55 ` John Stultz
2011-05-07 16:30 ` Ted Ts'o
2011-05-07 16:30 ` Ted Ts'o
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=20110504164257.5bb61879.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=john.stultz@linaro.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.