From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] treewide: fix memory corruptions when TASK_COMM_LEN != 16
Date: Thu, 23 Feb 2012 09:30:27 -0800 [thread overview]
Message-ID: <20120223093027.7dfc90e3.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1202231152280.9220@frira.zrqbmnf.qr>
On Thu, 23 Feb 2012 12:19:28 +0100 (CET) Jan Engelhardt <jengelh@medozas.de> wrote:
>
> On Thursday 2012-02-23 10:57, Andrew Morton wrote:
> >>
> But there's more,
> >>
> >> 24931 ? S 0:00 \_ [btrfs-endio-met]
> \_ [kconservative/5]
> \_ [ext4-dio-unwrit]
> >>
> >> [with a wondersome patch:] $ grep Name /proc/{29431,29432}/stat*
> >> /proc/29431/status:Name: btrfs-endio-meta-1
> >> /proc/29432/status:Name: btrfs-endio-meta-write-1
> Name: kconservative/512
> Name: ext4-dio-unwritten
> >
> >doh. The fix for that is to have less clueless btrfs developers.
>
> And truncate their names to SUNWbtfs, ORCLintg and EXT4diou?
> I think not :)
Teach ps(1) to look in /proc/pid/status for kernel threads?
next prev parent reply other threads:[~2012-02-23 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 22:09 [PATCH 1/2] treewide: fix memory corruptions when TASK_COMM_LEN != 16 Jan Engelhardt
2012-01-21 22:09 ` [PATCH 2/2] treewide: avoid truncation of process name Jan Engelhardt
2012-01-24 21:54 ` [PATCH 1/2] treewide: fix memory corruptions when TASK_COMM_LEN != 16 Andrew Morton
2012-02-01 1:15 ` Jan Engelhardt
2012-02-01 1:23 ` Andrew Morton
2012-02-01 1:35 ` Jan Engelhardt
2012-02-01 1:49 ` Andrew Morton
2012-02-01 2:15 ` Jan Engelhardt
2012-02-01 3:01 ` Andrew Morton
2012-02-22 12:48 ` Jan Engelhardt
2012-02-22 20:58 ` Andrew Morton
2012-02-23 9:09 ` Jan Engelhardt
2012-02-23 9:57 ` Andrew Morton
2012-02-23 11:19 ` Jan Engelhardt
2012-02-23 17:30 ` Andrew Morton [this message]
2012-02-23 21:59 ` Jan Engelhardt
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=20120223093027.7dfc90e3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jengelh@medozas.de \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).