From: ZhangZhen <zhenzhang.zhang@huawei.com>
To: Jan Kara <jack@suse.cz>
Cc: <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext3: fix some wrong comments
Date: Mon, 3 Mar 2014 09:44:02 +0800 [thread overview]
Message-ID: <5313DE62.9050802@huawei.com> (raw)
In-Reply-To: <20140228083710.GC28074@quack.suse.cz>
On 2014/2/28 16:37, Jan Kara wrote:
> On Fri 28-02-14 15:28:59, ZhangZhen wrote:
>> The comments in the code are wrong, because every generic_file_write()
>> is replaced by generic_file_aio_write().
>>
>> Signed-off-by: Zhang Zhen <zhenzhang.zhang@huawei.com>
>> ---
>> fs/ext3/inode.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/ext3/inode.c b/fs/ext3/inode.c
>> index 384b6eb..0b94832 100644
>> --- a/fs/ext3/inode.c
>> +++ b/fs/ext3/inode.c
>> @@ -1574,7 +1574,7 @@ static int buffer_unmapped(handle_t *handle, struct buffer_head *bh)
>> *
>> * Similar for:
>> *
>> - * ext3_file_write() -> generic_file_write() -> __alloc_pages() -> ...
>> + * ext3_file_write() -> generic_file_aio_write() -> __alloc_pages() -> ...
> Well, but ext3_file_write() doesn't exist either so the comment obviously
> needs further updates.
>
>> *
>> * Same applies to ext3_get_block(). We will deadlock on various things like
>> * lock_journal and i_truncate_mutex.
>> @@ -3212,7 +3212,7 @@ out_brelse:
>> *
>> * We are called from a few places:
>> *
>> - * - Within generic_file_write() for O_SYNC files.
>> + * - Within generic_file_aio_write() for O_SYNC files.
>> * Here, there will be no transaction running. We wait for any running
>> * transaction to commit.
>> *
> This is correct but as I'm looking through the comment it needs much
> larger update. So something like attached patches looks more appropriate.
> Thanks for pointing me to those outdated comments.
>
> Honza
>
Hi Honza,
Your fix is more better than mine. It's a good chance for me to learn, thanks!
Zhen
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-03-03 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53100429.3000205@huawei.com>
2014-02-28 7:28 ` [PATCH] ext3: fix some wrong comments ZhangZhen
2014-02-28 8:37 ` Jan Kara
2014-03-03 1:44 ` ZhangZhen [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=5313DE62.9050802@huawei.com \
--to=zhenzhang.zhang@huawei.com \
--cc=jack@suse.cz \
--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