From: Ted Ts'o <tytso@mit.edu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: fix callers of ext4_handle_release_buffer() API
Date: Sun, 20 Mar 2011 22:43:24 -0400 [thread overview]
Message-ID: <20110321024324.GF4135@thunk.org> (raw)
In-Reply-To: <AANLkTi=KXX9zjBKSGs18OpZUzOD-yyKj9hNVSBi_iBAB@mail.gmail.com>
On Tue, Mar 01, 2011 at 03:30:24PM +0200, Amir Goldstein wrote:
> ext4_handle_release_buffer() is an API, which is not being used properly.
> This is not so bad considering that it calls jbd2_journal_release_buffer(),
> which does nothing, but the snapshots implementation of this API does
> something.
>
> ext4_jbd2.h defines 2 identical wrapper functions:
> ext4_journal_release_buffer() and ext4_handle_release_buffer().
> The former has no callers, so it was removed.
Note that there are some commented-out calls to
ext4_journal_release_buffer() in resize.c; they're probably commented
out because at least today, jbd2_journal_release_buffer() is indeed a
no-op.
I'll update resize.c to use the preferred call. Speaking of which,
how does on-line resize work in the face of the snapshot feature? Is
that something that is or isn't supported?
Note also that there may be places where a buffer has
get_write_access() called on it, only for it to be never modified.
resize.c is an example of that.
> There are 2 users of the API:
> ext4_new_inode() calls ext4_handle_release_buffer() and
> ext4_xattr_block_set() calls jbd2_journal_release_buffer() directly.
> The latter was chagned to call the wrapper API.
>
> Signed-off-by: Amir Goldstein <amir73il@users.sf.net>
I'll apply this patch the changes.
- Ted
next prev parent reply other threads:[~2011-03-21 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 13:30 [PATCH] ext4: fix callers of ext4_handle_release_buffer() API Amir Goldstein
2011-03-21 2:43 ` Ted Ts'o [this message]
2011-03-21 4:34 ` Amir Goldstein
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=20110321024324.GF4135@thunk.org \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox