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 01:57:26 -0800 [thread overview]
Message-ID: <20120223015726.cb065d73.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1202222303190.15465@frira.zrqbmnf.qr>
On Thu, 23 Feb 2012 10:09:33 +0100 (CET) Jan Engelhardt <jengelh@medozas.de> wrote:
> On Wednesday 2012-02-22 21:58, Andrew Morton wrote:
>
> >On Wed, 22 Feb 2012 13:48:08 +0100 (CET)
> >Jan Engelhardt <jengelh@medozas.de> wrote:
> >
> >> task: provide a larger task command buffer
> >
> ><scratches head>
> >
> >Why are we bothering ourselves about this?
>
> Some prefer to know what's going on in the system. Every other or
> so kernel release there are some new happy kthreads, such as
>
> 24930 ? S 0:00 \_ [btrfs-endio-1]
> 24931 ? S 0:00 \_ [btrfs-endio-met]
> 24932 ? S 0:00 \_ [btrfs-endio-met]
> 24933 ? S 0:00 \_ [btrfs-endio-wri]
> 24934 ? S 0:00 \_ [btrfs-freespace]
>
> at which point one is curious to find out the rest of the met and why
> there are two of them. If expanded one actually sees they are different
> kthreads (rather than just per-cpu instances for a WQ, for example)
>
> $ grep Name /proc/{29431,29432}/stat*
> /proc/29431/status:Name: btrfs-endio-meta-1
> /proc/29432/status:Name: btrfs-endio-meta-write-1
>
> That's all.
doh. The fix for that is to have less clueless btrfs developers.
next prev parent reply other threads:[~2012-02-23 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 22:09 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 [this message]
2012-02-23 11:19 ` Jan Engelhardt
2012-02-23 17:30 ` Andrew Morton
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=20120223015726.cb065d73.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
Powered by JetHome