From: Andrew Morton <akpm@osdl.org>
To: Chris Sykes <chris@sigsegv.plus.com>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: Hang during rm on ext2 mounted sync (2.6.14-rc2+)
Date: Sat, 24 Sep 2005 10:39:46 -0700 [thread overview]
Message-ID: <20050924103946.540d708d.akpm@osdl.org> (raw)
In-Reply-To: <20050924142825.GA5158@sigsegv.plus.com>
Chris Sykes <chris@sigsegv.plus.com> wrote:
>
> On Sat, Sep 24, 2005 at 01:14:31PM +0100, Chris Sykes wrote:
> > After many compile reboot cycles, git-bisect tells me that the
> > offending cset is 10f47e6a1b8b276323b652053945c87a63a5812d:
> > [PATCH] ext2: Enable atomic inode security labeling
> >
> > I'll do some more testing to verify.
>
> Latest kernel from git (2.6.14-rc2-g87e807b6) still causes the problem
> for me. Reversing cset 10f47e6a1b8b276323b652053945c87a63a5812d fixes
> it for me.
Good stuff, thanks.
> I'll build a kernel with CONFIG_EXT2_FS_XATTR disabled and see if that
> also makes the issue go away.
Yup. I thought I already tested wth your .config?
next prev parent reply other threads:[~2005-09-24 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:37 Hang during rm on ext2 mounted sync (2.6.14-rc2+) Chris Sykes
2005-09-22 20:49 ` Chris Sykes
2005-09-23 8:57 ` Andrew Morton
2005-09-23 12:19 ` Chris Sykes
2005-09-23 13:22 ` Chris Sykes
2005-09-23 19:18 ` Andrew Morton
2005-09-23 19:45 ` Jesper Juhl
2005-09-23 19:47 ` Andrew Morton
2005-09-23 20:11 ` Alexey Dobriyan
2005-09-23 20:06 ` Jesper Juhl
2005-09-23 20:23 ` Andrew Morton
2005-09-23 20:51 ` Jesper Juhl
2005-09-24 12:14 ` Chris Sykes
2005-09-24 14:28 ` Chris Sykes
2005-09-24 15:47 ` [PATCH]: Fix ext2_new_inode() failure paths Chris Sykes
2005-09-24 17:33 ` [PATCH]: Fix ext3_new_inode() " Chris Sykes
2005-09-24 17:39 ` Andrew Morton [this message]
2005-09-25 10:56 ` Hang during rm on ext2 mounted sync (2.6.14-rc2+) Chris Sykes
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=20050924103946.540d708d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=chris@sigsegv.plus.com \
--cc=ext2-devel@lists.sourceforge.net \
--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