From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Brian Foster <bfoster@redhat.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
fstests <fstests@vger.kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3 3/3] xfs: test readlink/readdir with malformed inode mode
Date: Wed, 11 Jan 2017 08:38:45 +0200 [thread overview]
Message-ID: <CAOQ4uxhoDdfoh0-OMkNgB6VEOpeOO5qj1GG9=D+cXpi6XLPQkA@mail.gmail.com> (raw)
In-Reply-To: <1483968625-29160-4-git-send-email-amir73il@gmail.com>
On Mon, Jan 9, 2017 at 3:30 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> In addition to testing xfs_repair on inodes with malformed mode,
> and fstat of those inodes on a mounted fs, try to also list content
> of mock directory and readlink of mock symlink.
>
> Readdir of mock directory triggers XFS assertion on kernel 4.9 with
> XFS_DEBUG=y
>
> XFS: Assertion failed:
> rval == 0 || args->dp->i_d.di_size == args->geo->blksize,
> file: /home/amir/build/src/linux/fs/xfs/libxfs/xfs_dir2.c, line: 634
>
> A fix patch, as suggested by Darrick, changes this ASSERT() to
> return -EFSCORRUPTED ("xfs: sanity check directory inode di_size").
>
> Merging this test should be deferred to after fix patch is merged.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> tests/xfs/348 | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/tests/xfs/348 b/tests/xfs/348
> index 30825a4..20d5d7e 100755
> --- a/tests/xfs/348
> +++ b/tests/xfs/348
> @@ -133,6 +133,15 @@ for dt in $dtypes; do
> cat $tmp.stat.err
> else
> echo "stat: '$testdir/$file' is a $ftype"
> + # Verify that readlink of a file posing as a symlink
> + # and ls of a file posing as a directory does not blow up.
> + # NOTE that ls DOES ASSERT with kernel 4.9 and XFS_DEBUG=y
> + # on malformed directory
> + if [ -d $testdir/$file ]; then
> + ls "$safety" $testdir/$file &> /dev/null
leftover: "$safety"
> + elif [ -h $testdir/$file ]; then
> + readlink $testdir/$file &> /dev/null
> + fi
> fi | _filter_scratch
> done
> _scratch_unmount
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-01-11 6:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 13:30 [PATCH v3 0/3] xfs: test malformed inode mode Amir Goldstein
2017-01-09 13:30 ` [PATCH v3 1/3] xfs: test handling of invalid inode modes Amir Goldstein
2017-01-09 13:36 ` Amir Goldstein
2017-01-09 13:39 ` Amir Goldstein
2017-01-09 13:30 ` [PATCH v3 2/3] xfs: test fstat with malformed inode mode Amir Goldstein
2017-01-09 13:30 ` [PATCH v3 3/3] xfs: test readlink/readdir " Amir Goldstein
2017-01-11 6:38 ` Amir Goldstein [this message]
2017-01-11 6:41 ` Amir Goldstein
2017-01-20 5:25 ` [PATCH v3 0/3] xfs: test " 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='CAOQ4uxhoDdfoh0-OMkNgB6VEOpeOO5qj1GG9=D+cXpi6XLPQkA@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.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).