From: Liu Bo <bo.li.liu@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: bail out gracefully rather than BUG_ON
Date: Tue, 31 Oct 2017 14:51:36 -0700 [thread overview]
Message-ID: <20171031215136.GA17979@lim.localdomain> (raw)
In-Reply-To: <d2dc51f8-2cbb-c425-a712-93ee41de4b1a@suse.com>
On Tue, Oct 31, 2017 at 10:23:30PM +0200, Nikolay Borisov wrote:
>
>
> On 30.10.2017 19:14, Liu Bo wrote:
> > If a file's DIR_ITEM key is invalid (due to memory errors) and gets
> > written to disk, a future lookup_path can end up with kernel panic due
> > to BUG_ON().
> >
> > This gets rid of the BUG_ON(), meanwhile output the corrupted key and
> > return ENOENT if it's invalid.
> >
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > The diff doesn't show the logic well, 'goto out_err' will return with
> > assigning 0 to location->objectid, and the caller already has a check
> > for (location->objectid == 0) to return -ENOENT.
> >
> > fs/btrfs/inode.c | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> > index d94e3f6..916cdc9 100644
> > --- a/fs/btrfs/inode.c
> > +++ b/fs/btrfs/inode.c
> > @@ -5500,6 +5500,14 @@ static int btrfs_inode_by_name(struct inode *dir, struct dentry *dentry,
> > goto out_err;
> >
> > btrfs_dir_item_key_to_cpu(path->nodes[0], di, location);
> > + if (location->type != BTRFS_INODE_ITEM_KEY &&
> > + location->type != BTRFS_ROOT_ITEM_KEY) {
> > + btrfs_warn(root->fs_info,
> > + "%s gets something invalid in DIR_ITEM (name %s, directory ino %llu, location(%llu %u %llu))",
> > + __func__, name, btrfs_ino(BTRFS_I(dir)),
> > + location->objectid, location->type, location->offset);
> > + goto out_err;
>
> If this situation happens it's possible that ret is still 0 so the error
> handling in btrfs_lookup_dentry might not trigger. How about just
> setting -EUCLEAN if we execute the if branch?
>
Thanks for the comment. So it's not going to trigger the (ret < 0)
check, instead it tries to trigger the one following (ret < 0):
if (location.objectid == 0)
return ERR_PTR(-ENOENT);
which is consistent to the case when we didn't find the btrfs_dir_item
(di is NULL, returned by btrfs_lookup_dir_item()).
thanks,
-liubo
> > + }
> > out:
> > btrfs_free_path(path);
> > return ret;
> > @@ -5816,8 +5824,6 @@ struct inode *btrfs_lookup_dentry(struct inode *dir, struct dentry *dentry)
> > return inode;
> > }
> >
> > - BUG_ON(location.type != BTRFS_ROOT_ITEM_KEY);
> > -
> > index = srcu_read_lock(&fs_info->subvol_srcu);
> > ret = fixup_tree_root_location(fs_info, dir, dentry,
> > &location, &sub_root);
> >
next prev parent reply other threads:[~2017-10-31 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 17:14 [PATCH] Btrfs: bail out gracefully rather than BUG_ON Liu Bo
2017-10-30 18:25 ` Liu Bo
2017-10-31 20:23 ` Nikolay Borisov
2017-10-31 21:51 ` Liu Bo [this message]
2017-11-01 6:20 ` Nikolay Borisov
2017-11-13 17:19 ` David Sterba
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=20171031215136.GA17979@lim.localdomain \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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).