From: Anatoly Pugachev <matorola@gmail.com>
To: dsterba@suse.cz, "Anatoly Pugachev" <matorola@gmail.com>,
"Holger Hoffstätte" <holger@applied-asynchrony.com>,
"Omar Sandoval" <osandov@osandov.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
kernel-team@fb.com,
"Chandan Rajendra" <chandan@linux.vnet.ibm.com>,
bo.li.liu@oracle.com, fstests@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Btrfs: free space tree and sanity test fixes
Date: Sat, 1 Oct 2016 12:26:35 +0300 [thread overview]
Message-ID: <CADxRZqwZ6ymxL4x9455HFH95px=bjuqKKfBrO9BO7y1VBkvrYw@mail.gmail.com> (raw)
In-Reply-To: <20160929142945.GC5531@suse.cz>
On Thu, Sep 29, 2016 at 5:29 PM, David Sterba <dsterba@suse.cz> wrote:
> On Thu, Sep 29, 2016 at 04:02:35PM +0300, Anatoly Pugachev wrote:
>> > Try to add https://patchwork.kernel.org/patch/9332707/ aka
>> > "Btrfs: improve check_node to avoid reading corrupted nodes" which should return
>> > -EIO and prevent the BUG().
>>
>> Guys,
>>
>> I was wrong with "Btrfs: remove unnecessary btrfs_mark_buffer_dirty in
>> split_leaf" , because I've used patch from email
>> https://marc.info/?l=linux-btrfs&m=147319873029152&w=2 which patches
>> fs/btrfs/ctree.c , but forgot to apply kdave git kernel commit
>> 1ba98d086fe3a14d6a31f2f66dbab70c45d00f63 "Btrfs: detect corruption
>> when non-root leaf has zero item"
>>
>> :-/
>>
>> Should I remake all the tests?
>
> It would be much appreciated, as we probably won't get any other sparc64
> testing. Thanks.
David,
just tried to apply 1ba98d086fe3a14d6a31f2f66dbab70c45d00f63 "Btrfs:
detect corruption when non-root leaf has zero item"
from your btrfs development kernel tree, and patch command said that
it already applied...
mator@ttip:~/linux-2.6$ git remote -v
origin git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(fetch)
origin git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(push)
mator@ttip:~/linux-2.6$ git show -s --oneline
1ba98d086fe3a14d6a31f2f66dbab70c45d00f63
1ba98d0 Btrfs: detect corruption when non-root leaf has zero item
So my tests was correct and included all the needed patches?!
Sorry for the mess. :-/
I'm going to check patch suggested by Holger Hoffstätte ,
https://patchwork.kernel.org/patch/9332707/ ...
next prev parent reply other threads:[~2016-10-01 9:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 0:22 [PATCH v2 0/6] Btrfs: free space tree and sanity test fixes Omar Sandoval
2016-09-23 0:24 ` [PATCH v2 1/6] Btrfs: fix free space tree bitmaps on big-endian systems Omar Sandoval
2016-09-23 14:37 ` Holger Hoffstätte
2016-09-23 0:24 ` [PATCH v2 2/6] Btrfs: fix mount -o clear_cache,space_cache=v2 Omar Sandoval
2016-09-23 14:37 ` Holger Hoffstätte
2016-09-23 0:24 ` [PATCH v2 3/6] Btrfs: catch invalid free space trees Omar Sandoval
2016-09-23 14:40 ` Holger Hoffstätte
2016-09-24 19:50 ` Hans van Kranenburg
2016-09-26 17:39 ` Omar Sandoval
2016-09-26 17:46 ` Hans van Kranenburg
2016-09-26 17:52 ` Omar Sandoval
2016-09-26 23:13 ` Omar Sandoval
2016-09-29 11:43 ` David Sterba
2016-09-23 0:24 ` [PATCH v2 4/6] Btrfs: fix extent buffer bitmap tests on big-endian systems Omar Sandoval
2016-09-23 0:24 ` [PATCH v2 5/6] Btrfs: expand free space tree sanity tests to catch endianness bug Omar Sandoval
2016-09-23 0:24 ` [PATCH v2 6/6] Btrfs: use less memory for delalloc sanity tests Omar Sandoval
2016-09-23 9:27 ` David Sterba
2016-09-23 16:52 ` Omar Sandoval
2016-09-23 21:22 ` Omar Sandoval
2016-09-26 15:58 ` David Sterba
2016-09-26 17:33 ` Omar Sandoval
2016-09-25 7:55 ` [PATCH v2 0/6] Btrfs: free space tree and sanity test fixes Anatoly Pugachev
2016-09-26 17:50 ` David Sterba
2016-09-26 17:56 ` Omar Sandoval
2016-09-29 12:21 ` Anatoly Pugachev
2016-09-29 12:52 ` Holger Hoffstätte
2016-09-29 13:02 ` Anatoly Pugachev
2016-09-29 14:29 ` David Sterba
2016-10-01 9:26 ` Anatoly Pugachev [this message]
2016-09-26 17:51 ` Omar Sandoval
2016-09-28 13:03 ` Chandan Rajendra
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='CADxRZqwZ6ymxL4x9455HFH95px=bjuqKKfBrO9BO7y1VBkvrYw@mail.gmail.com' \
--to=matorola@gmail.com \
--cc=bo.li.liu@oracle.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=dsterba@suse.cz \
--cc=fstests@vger.kernel.org \
--cc=holger@applied-asynchrony.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.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).