From: Dave Chinner <david@fromorbit.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] xfs: test inode allocation state missmatch corruption
Date: Sat, 12 May 2018 09:32:39 +1000 [thread overview]
Message-ID: <20180511233239.GZ23861@dastard> (raw)
In-Reply-To: <20180511161127.15158-1-zlang@redhat.com>
On Sat, May 12, 2018 at 12:11:27AM +0800, Zorro Lang wrote:
> There's a situation where the directory structure and the inobt
> thinks the inode is free, but the inode on disk thinks it is still
> in use. XFS should detect it and prevent the kernel from oopsing
> on lookup.
Isn't this testing the same thing that I recently posted "xfs: test
inobt/on disk free state mismatches" for?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-05-11 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 16:11 [PATCH v2] xfs: test inode allocation state missmatch corruption Zorro Lang
2018-05-11 23:32 ` Dave Chinner [this message]
2018-05-12 13:18 ` Zorro Lang
2018-05-16 8:18 ` Zorro Lang
2018-05-18 3:59 ` Dave Chinner
2018-05-18 5:26 ` Zorro Lang
-- strict thread matches above, loose matches on Subject: below --
2018-05-21 1:58 Zorro Lang
2018-05-21 9:04 ` Eryu Guan
2018-05-21 15:55 ` Darrick J. Wong
2018-05-21 22:50 ` Dave Chinner
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=20180511233239.GZ23861@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=zlang@redhat.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