From: Jan Kara <jack@suse.cz>
To: Chenyuan Mi <cymi20@fudan.edu.cn>
Cc: yuanxzhang@fudan.edu.cn, Xiyu Yang <xiyuyang19@fudan.edu.cn>,
Xin Tan <tanxin.ctf@gmail.com>, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix handle refcount leak in ext4_write_begin()
Date: Thu, 7 Oct 2021 16:06:40 +0200 [thread overview]
Message-ID: <20211007140640.GA2670@quack2.suse.cz> (raw)
In-Reply-To: <20210908070640.7135-1-cymi20@fudan.edu.cn>
On Wed 08-09-21 15:06:40, Chenyuan Mi wrote:
> The reference counting issue happens when ret is zero,
> the function forgets to decrease the refcount of handle
> increased by ext4_journal_start().
>
> Fix this issue by using ext4_journal_stop() to decrease
> the refcount of handle.
>
> Signed-off-by: Chenyuan Mi <cymi20@fudan.edu.cn>
> Signed-off-by: Xiyu Yang <xiyuyang19@fudan.edu.cn>
> Signed-off-by: Xin Tan <tanxin.ctf@gmail.com>
Yes, but that is deliberate. We want to keep the transaction running until
the write is done - i.e., until ->write_end() callback where we call
ext4_journal_stop(). As a side note, please test your patches. You clearly
didn't test this patch because if you did, you would notice that your patch
breaks writing to ext4.
Honza
> ---
> fs/ext4/inode.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index d18852d6029c..90c57d8e3de1 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -1249,6 +1249,7 @@ static int ext4_write_begin(struct file *file, struct address_space *mapping,
> put_page(page);
> return ret;
> }
> + ext4_journal_stop(handle);
> *pagep = page;
> return ret;
> }
> --
> 2.17.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2021-10-07 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 7:06 Chenyuan Mi
2021-10-07 14:06 ` Jan Kara [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=20211007140640.GA2670@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=cymi20@fudan.edu.cn \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tanxin.ctf@gmail.com \
--cc=tytso@mit.edu \
--cc=xiyuyang19@fudan.edu.cn \
--cc=yuanxzhang@fudan.edu.cn \
/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
all inboxes | Powered by JetHome®