From: Theodore Tso <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext4: partial revert to fix double brelse WARNING()
Date: Sat, 7 Nov 2009 03:11:16 -0500 [thread overview]
Message-ID: <20091107081116.GG26342@mit.edu> (raw)
In-Reply-To: <1257579823-31295-1-git-send-email-tytso@mit.edu>
On Sat, Nov 07, 2009 at 02:43:42AM -0500, Theodore Ts'o wrote:
> This is a partial revert of commit 6487a9d (only the changes made to
> fs/ext4/namei.c), since it is causing the following brelse() of an
> already free buffer when running fsstress on a file system with 1k
> blocksize:
This description isn't quite right. I did get this error while
running fsstress on a file system with a 1k blocksize, but the real
problem was that I was using a device that wasn't big enough for
fsstress, and it was really an ENOSPC error while extending a
directory from 1 block. Curt's patch didn't take into account that
the call to ext4_append() in make_indexed_dir() could also return
ENOSPC, that would cause a double brelse().
I suppose I could have fixed it up by adding an explicit check for
ENOSPC and not freeing the buffer head in that one return path, which
would have made for a smaller patch, but the resulting code would be
really horrible. So I still think the best thing to do for now is to
partially revert commit 6487a9d now, and fix things up cleanly after
2.6.32 is released.
- Ted
prev parent reply other threads:[~2009-11-07 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 7:43 [PATCH 1/2] ext4: partial revert to fix double brelse WARNING() Theodore Ts'o
2009-11-07 7:43 ` [PATCH 2/2] ext4: Fix potential buffer head leak when add_dirent_to_buf() returns ENOSPC Theodore Ts'o
2009-11-07 8:11 ` Theodore Tso [this message]
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=20091107081116.GG26342@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@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.