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 v4 0/4] btrfs: Enhanced runtime defence against fuzzed images
Date: Wed, 12 Aug 2020 08:52:14 +0200 [thread overview]
Message-ID: <20200812065214.GX2026@twin.jikos.cz> (raw)
In-Reply-To: <20200812060509.71590-1-wqu@suse.com>
On Wed, Aug 12, 2020 at 02:05:05PM +0800, Qu Wenruo wrote:
> v4:
> - Remove one patch which is already merged
> A little surprised by the fact that git can't detecth such case.
I've looked at it and that's a normal patch from git perspective,
there's not even a conflict in the context, you're adding a new hunk.
That it's the same one that's a few lines below is caused by
intermediate changes, but that's what happens with any other patch.
next prev parent reply other threads:[~2020-08-12 6:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 6:05 [PATCH v4 0/4] btrfs: Enhanced runtime defence against fuzzed images Qu Wenruo
2020-08-12 6:05 ` [PATCH v4 1/4] btrfs: extent_io: Do extra check for extent buffer read write functions Qu Wenruo
2020-08-13 14:05 ` David Sterba
2020-08-14 0:47 ` Qu Wenruo
2020-08-14 10:29 ` David Sterba
2020-08-12 6:05 ` [PATCH v4 2/4] btrfs: extent-tree: Kill BUG_ON() in __btrfs_free_extent() and do better comment Qu Wenruo
2020-08-13 14:10 ` David Sterba
2020-08-14 0:52 ` Qu Wenruo
2020-08-14 8:01 ` David Sterba
2020-08-14 8:07 ` Qu Wenruo
2020-08-12 6:05 ` [PATCH v4 3/4] btrfs: extent-tree: Kill the BUG_ON() in insert_inline_extent_backref() Qu Wenruo
2020-08-12 6:05 ` [PATCH v4 4/4] btrfs: ctree: Checking key orders before merged tree blocks Qu Wenruo
2020-08-13 14:21 ` David Sterba
2020-08-14 0:54 ` Qu Wenruo
2020-08-14 7:58 ` David Sterba
2020-08-12 6:52 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-12 6:02 [PATCH v4 0/4] btrfs: Enhanced runtime defence against fuzzed images 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=20200812065214.GX2026@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