From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: initialize test inodes location
Date: Thu, 17 Dec 2020 15:41:09 +0100 [thread overview]
Message-ID: <20201217144109.GO6430@twin.jikos.cz> (raw)
In-Reply-To: <c779da25-61f3-85fb-b593-fdd614ab8931@toxicpanda.com>
On Thu, Dec 17, 2020 at 09:39:18AM -0500, Josef Bacik wrote:
> On 12/17/20 7:41 AM, David Sterba wrote:
> > On Tue, Dec 15, 2020 at 12:00:26PM -0500, Josef Bacik wrote:
> >> While testing other things I was noticing that sometimes my VM would
> >> fail to load the btrfs module because the self test failed like this
> >>
> >> BTRFS: selftest: fs/btrfs/tests/inode-tests.c:963 miscount, wanted 1, got 0
> >>
> >> This turned out to be because sometimes the btrfs ino would be the btree
> >> inode number, and thus we'd skip calling the set extent delalloc bit
> >> helper, and thus not adjust ->outstanding_extents. Fix this by making
> >> sure we init test inodes with a valid inode number so that we don't get
> >> random failures during self tests.
> >>
> >> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> >> ---
> >> fs/btrfs/tests/btrfs-tests.c | 7 ++++++-
> >> fs/btrfs/tests/inode-tests.c | 9 ---------
> >> 2 files changed, 6 insertions(+), 10 deletions(-)
> >>
> >> diff --git a/fs/btrfs/tests/btrfs-tests.c b/fs/btrfs/tests/btrfs-tests.c
> >> index 8ca334d554af..0fede1514a3e 100644
> >> --- a/fs/btrfs/tests/btrfs-tests.c
> >> +++ b/fs/btrfs/tests/btrfs-tests.c
> >> @@ -55,8 +55,13 @@ struct inode *btrfs_new_test_inode(void)
> >> struct inode *inode;
> >>
> >> inode = new_inode(test_mnt->mnt_sb);
> >> - if (inode)
> >> + if (inode) {
> >> + inode->i_mode = S_IFREG;
> >> + BTRFS_I(inode)->location.type = BTRFS_INODE_ITEM_KEY;
> >> + BTRFS_I(inode)->location.objectid = BTRFS_FIRST_FREE_OBJECTID;
> >> + BTRFS_I(inode)->location.offset = 0;
> >> inode_init_owner(inode, NULL, S_IFREG);
> >> + }
> >
> > As this is adding more statements to the if-block, I'd rather rewrite it
> > as
> >
> > inode = new();
> > if (!inode)
> > return NULL;
> >
> > inode-> ...
> >
>
> Agreed, I've updated it locally, I'll wait for comments for the rest of the
> series and then resend. Thanks,
No need to resend unless something else pops up, the change is trivial.
prev parent reply other threads:[~2020-12-17 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 17:00 [PATCH] btrfs: initialize test inodes location Josef Bacik
2020-12-17 12:41 ` David Sterba
2020-12-17 14:39 ` Josef Bacik
2020-12-17 14:41 ` 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=20201217144109.GO6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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