From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Qu Wenruo <wqu@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/4] btrfs-progs: check/lowmem: add the ability to repair extent item generation
Date: Mon, 10 Aug 2020 15:35:06 +0800 [thread overview]
Message-ID: <dd7cc94b-102c-ab8b-662c-b9fbe7449b7a@gmx.com> (raw)
In-Reply-To: <SN4PR0401MB35989D15F1724F55E26DD13E9B440@SN4PR0401MB3598.namprd04.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 362 bytes --]
On 2020/8/10 下午3:30, Johannes Thumshirn wrote:
> On 10/08/2020 09:27, Qu Wenruo wrote:
>> + if ((tmp_err & (INVALID_GENERATION) && repair)){
>
> Shouldn't this be 'if ((tmp_err & INVALID_GENERATION) && repair) {'
>
Nice catch!
Will fix it in next update, since I also found the patch name for the
4th patch has a typo...
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-10 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 7:27 [PATCH 0/4] btrfs-progs: check: add the ability to repair extent item generation corruption Qu Wenruo
2020-08-10 7:27 ` [PATCH 1/4] btrfs-progs: check/lowmem: add the ability to repair extent item generation Qu Wenruo
2020-08-10 7:30 ` Johannes Thumshirn
2020-08-10 7:35 ` Qu Wenruo [this message]
2020-08-10 7:27 ` [PATCH 2/4] btrfs-progs: check/original: don't reset extent generation for check_block() Qu Wenruo
2020-08-10 7:27 ` [PATCH 3/4] btrfs-progs: check/original: add the ability to repair extent item generation Qu Wenruo
2020-08-10 7:27 ` [PATCH 4/4] btrfs-progs: tests/fsck: enhance invalid extent item geneartion test cases 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=dd7cc94b-102c-ab8b-662c-b9fbe7449b7a@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=Johannes.Thumshirn@wdc.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