From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, Luciano Chavez <chavez@us.ibm.com>
Subject: Re: [PATCH] btrfs: inode: Fix NULL pointer dereference if inode doesn't need compression
Date: Tue, 28 Jul 2020 15:41:21 +0200 [thread overview]
Message-ID: <20200728134121.GV3703@twin.jikos.cz> (raw)
In-Reply-To: <c0e68f16-a55b-bf4c-47fe-289f83210847@gmx.com>
On Tue, Jul 28, 2020 at 09:26:43PM +0800, Qu Wenruo wrote:
> >> Fixes: 4d3a800ebb12 ("btrfs: merge nr_pages input and output parameter in compress_pages")
> >
> > How does this patch cause the bug?
> >
> Sorry, I should explain more on that.
>
> In fact it takes me quite some time to find the proper culprit.
>
> Before that commit, we have @nr_pages_ret initialized to 0 in
> compress_file_extent().
>
> If inode_need_compress() returned false in that function, we continue to
> the same inline file extent insert,.
>
> But in free_pages_out: tag, we use @nr_pages_nr to free pages, which is
> still 0, as it only get initialized to proper values after
> btrfs_compress_pages() call, which we skipped due to
> inode_need_compress() returned false.
>
> Then free_pages_out: tag will not execute the WARN_ON() and put_pages()
> calls, just skip to kfree(pages). And kfree() can handle NULL pointers
> without any problem.
>
> Thus a completely sane looking cleanup in fact caused the NULL pointer
> dereference regression for race cases.
Thanks. It was not obvious so I was expecting a bit more convoluted way
to hit the bug.
next prev parent reply other threads:[~2020-07-28 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 8:39 [PATCH] btrfs: inode: Fix NULL pointer dereference if inode doesn't need compression Qu Wenruo
2020-07-28 13:19 ` David Sterba
2020-07-28 13:26 ` Qu Wenruo
2020-07-28 13:41 ` David Sterba [this message]
2020-08-02 19:16 ` Nikolay Borisov
2020-08-02 23:14 ` Qu Wenruo
2020-08-25 15:03 ` David Sterba
2020-08-04 6:41 ` Qu Wenruo
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=20200728134121.GV3703@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=chavez@us.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.com \
/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