From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, Jungyeon Yoon <jungyeon.yoon@gmail.com>
Subject: Re: [PATCH v5 0/4] btrfs: Enhanced runtime defence against fuzzed images
Date: Thu, 27 Aug 2020 16:47:50 +0200 [thread overview]
Message-ID: <20200827144750.GN28318@twin.jikos.cz> (raw)
In-Reply-To: <20200819063550.62832-1-wqu@suse.com>
On Wed, Aug 19, 2020 at 02:35:46PM +0800, Qu Wenruo wrote:
> v5:
> - Properly inline the check while make the report code into another
> function for the 1st patch
>
> - Keep btrfs_abort_transaction() call where it is for the 2nd patch
> To make the line number correct and abort transaction asap.
>
> - Function naming update for the 4th patch
>
> Qu Wenruo (4):
> btrfs: extent_io: do extra check for extent buffer read write
> functions
> btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent() and do
> better comment
> btrfs: extent-tree: kill the BUG_ON() in
> insert_inline_extent_backref()
> btrfs: ctree: checking key orders before merged tree blocks
With several fixups and updates added to misc-next. Thanks.
prev parent reply other threads:[~2020-08-27 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 6:35 [PATCH v5 0/4] btrfs: Enhanced runtime defence against fuzzed images Qu Wenruo
2020-08-19 6:35 ` [PATCH v5 1/4] btrfs: extent_io: do extra check for extent buffer read write functions Qu Wenruo
2020-08-19 17:11 ` David Sterba
2020-08-19 23:14 ` Qu Wenruo
2020-08-20 9:50 ` David Sterba
2020-08-20 9:58 ` Qu Wenruo
2020-08-20 14:46 ` David Sterba
2020-08-20 15:18 ` David Sterba
2020-08-20 23:39 ` Qu Wenruo
2020-08-19 6:35 ` [PATCH v5 2/4] btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent() and do better comment Qu Wenruo
2020-08-19 6:35 ` [PATCH v5 3/4] btrfs: extent-tree: kill the BUG_ON() in insert_inline_extent_backref() Qu Wenruo
2020-08-19 6:35 ` [PATCH v5 4/4] btrfs: ctree: checking key orders before merged tree blocks Qu Wenruo
2020-08-27 14:47 ` David Sterba [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=20200827144750.GN28318@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=jungyeon.yoon@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).