From: "Theodore Ts'o" <tytso@mit.edu>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: fix bh leak on error paths in ext4_rename() and ext4_cross_rename()
Date: Thu, 2 Apr 2015 16:36:28 -0400 [thread overview]
Message-ID: <20150402203628.GB450@thunk.org> (raw)
In-Reply-To: <20150303111719.26916.92177.stgit@buzz>
On Tue, Mar 03, 2015 at 02:17:19PM +0300, Konstantin Khlebnikov wrote:
> Release references to buffer-heads if ext4_journal_start() fails.
>
> Signed-off-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
> Fixes: 5b61de757535 ("ext4: start handle at least possible moment when renaming files")
Thanks, applied.
- Ted
prev parent reply other threads:[~2015-04-02 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 11:17 [PATCH] ext4: fix bh leak on error paths in ext4_rename() and ext4_cross_rename() Konstantin Khlebnikov
2015-03-04 15:03 ` Jan Kara
2015-04-02 20:36 ` Theodore Ts'o [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=20150402203628.GB450@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-ext4@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