From: Andrew Morton <akpm@osdl.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: dev@openvz.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext3: ext3_symlink should use GFP_NOFS allocations inside
Date: Fri, 10 Mar 2006 12:21:46 -0800 [thread overview]
Message-ID: <20060310122146.1da0cf1d.akpm@osdl.org> (raw)
In-Reply-To: <441178CF.7040705@tls.msk.ru>
Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> Kirill Korotaev wrote:
> > This patch fixes illegal __GFP_FS allocation inside ext3
> > transaction in ext3_symlink().
> > Such allocation may re-enter ext3 code from
> > try_to_free_pages. But JBD/ext3 code keeps a pointer to current
> > journal handle in task_struct and, hence, is not reentrable.
> >
> > This bug led to "Assertion failure in journal_dirty_metadata()" messages.
> >
> > http://bugzilla.openvz.org/show_bug.cgi?id=115
>
> Is it the same bug as http://marc.theaimsgroup.com/?t=113870577100003&r=1&w=2 ?
>
yes.
next prev parent reply other threads:[~2006-03-10 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 17:19 Kirill Korotaev
2006-03-09 21:04 ` Al Viro
2006-03-10 13:02 ` Michael Tokarev
2006-03-10 20:21 ` Andrew Morton [this message]
2006-03-10 8:08 Kirill Korotaev
2006-03-10 8:31 ` Al Viro
2006-03-10 8:46 ` Kirill Korotaev
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=20060310122146.1da0cf1d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dev@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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