All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Collins <paul@briny.ondioline.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kjournald keeps reference to namespace
Date: Fri, 24 Feb 2006 22:01:40 +0000	[thread overview]
Message-ID: <87y80076wr.fsf@briny.internal.ondioline.org> (raw)
In-Reply-To: <20060224133605.7a8e86ca.akpm@osdl.org> (Andrew Morton's message of "Fri, 24 Feb 2006 13:36:05 -0800")

Andrew Morton <akpm@osdl.org> writes:

> Paul Collins <paul@briny.ondioline.org> wrote:
>>
>>  Herbert Poetzl <herbert@13thfloor.at> writes:
>> 
>>  > On Fri, Feb 17, 2006 at 05:54:28PM -0800, Andrew Morton wrote:
>>  >> I think it'd be better to convert ext3 to use the kthread API which
>>  >> appears to accidentally not have this problem, because such threads
>>  >> are parented by keventd, which were parented by init.
>>  >
>>  > sounds like a plan!
>> 
>>  Here's my attempt at such a conversion.  Since jbd doesn't seem to
>>  want to collect an exit status, I didn't bother with kthread_stop().
>
> Ah.  I already did something similar. 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm2/broken-out/jbd-convert-kjournald-to-kthread-api.patch

Sweet, I managed to get it right at least.

>>  I got overexcited and also embedded the journal device in the process
>>  name, but that's probably useless churn.  Looks nice in pstree though:
>> 
>>       |         `-kjournald/254:1
>
> We only have 15 chars for that string - the final one you have there is on
> the raggedy edge.

Oh well, it's not that useful anyway.  I can count the number of times
I've needed to kill a particular kjournald on the fingers of one head.

-- 
Dag vijandelijk luchtschip de huismeester is dood

  reply	other threads:[~2006-02-24 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18  1:35 kjournald keeps reference to namespace Herbert Poetzl
2006-02-18  1:54 ` Andrew Morton
2006-02-18  3:30   ` Herbert Poetzl
2006-02-24 21:28     ` Paul Collins
2006-02-24 21:36       ` Andrew Morton
2006-02-24 22:01         ` Paul Collins [this message]
2006-02-18 13:36 ` Björn Steinbrink
2006-02-18 16:32   ` Björn Steinbrink
2006-02-18 17:12     ` Björn Steinbrink
2006-02-19  2:32       ` Eric W. Biederman

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=87y80076wr.fsf@briny.internal.ondioline.org \
    --to=paul@briny.ondioline.org \
    --cc=akpm@osdl.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 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.