From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "Darrick J . Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Brian Foster <bfoster@redhat.com>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] xfs/348: test handling of malformed inode mode
Date: Tue, 3 Jan 2017 13:52:56 +0800 [thread overview]
Message-ID: <20170103055256.GK1859@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1482689376-23553-1-git-send-email-amir73il@gmail.com>
On Sun, Dec 25, 2016 at 08:09:33PM +0200, Amir Goldstein wrote:
> Eryu,
>
> I beefed up the initial test sent earlier today with more checks
> on mounted fs.
>
> The original patch testing only xfs_repair remains patch 1 in this series.
>
> Patch 2 adds fstat tests on mounted fs, which are safe on my test system.
>
> Patch 3 is explosive. It exposes an XFS assert, but I left a "safety pin"
> that needs to be commented out to reproduce the assert.
My kenrel config doesn't turn DEBUG on, so I don't see a kernel crash :)
I can push this test out after the fix lands in upstream, then I think
there's no need to leave a switch in the test.
Otherwise tests look good to me. But I'd like to have Darrick to review
too, as he had written many fuzzer tests and suggested this test :)
Thanks,
Eryu
>
> I will soon post my kernel configs and dmesg logs.
>
> Amir.
>
> v2:
> - test fstat with malformed inode mode
> - test readlink/readdir with malformed inode mode
>
> v1:
> - test xfs_repair with malformed inode mode
>
> Amir Goldstein (3):
> xfs/348: test handling of invalid inode modes
> xfs/348: test fstat with malformed inode mode
> xfs/348: test readlink/readdir with malformed inode mode
>
> tests/xfs/348 | 154 +++++++++++++++++++++++++++
> tests/xfs/348.out | 312 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/xfs/group | 1 +
> 3 files changed, 467 insertions(+)
> create mode 100755 tests/xfs/348
> create mode 100644 tests/xfs/348.out
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-01-03 5:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 18:09 [PATCH v2 0/3] xfs/348: test handling of malformed inode mode Amir Goldstein
2016-12-25 18:09 ` [PATCH v2 1/3] xfs/348: test handling of invalid inode modes Amir Goldstein
2017-01-03 20:36 ` Darrick J. Wong
2017-01-04 10:36 ` Amir Goldstein
2017-01-04 20:33 ` Darrick J. Wong
2016-12-25 18:09 ` [PATCH v2 2/3] xfs/348: test fstat with malformed inode mode Amir Goldstein
2016-12-25 18:09 ` [PATCH v2 3/3] xfs/348: test readlink/readdir " Amir Goldstein
2017-01-03 5:52 ` Eryu Guan [this message]
2017-01-11 6:45 ` [PATCH v2 0/3] xfs/348: test handling of " Amir Goldstein
2017-01-11 9:08 ` Eryu Guan
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=20170103055256.GK1859@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).