From: Eric Sandeen <sandeen@sandeen.net>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "Darrick J . Wong" <darrick.wong@oracle.com>,
Brian Foster <bfoster@redhat.com>, Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3] xfsprogs: replace xfs_mode_to_ftype table with switch statement
Date: Fri, 20 Jan 2017 14:33:58 -0600 [thread overview]
Message-ID: <62671831-e226-bcd9-8367-a3cbe3ca1e01@sandeen.net> (raw)
In-Reply-To: <CAOQ4uxjbYZh8Wr28kJiUX6bnTn-bxgApKOA7qxwrbDA=Y31sVg@mail.gmail.com>
On 1/20/17 4:58 AM, Amir Goldstein wrote:
> On Wed, Jan 11, 2017 at 6:23 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> On 1/11/17 12:30 AM, Amir Goldstein wrote:
>>> The size of the xfs_mode_to_ftype[] conversion table
>>> was too small to handle an invalid value of mode=S_IFMT.
>>>
>>> Instead of fixing the table size, replace the conversion table
>>> with a conversion helper that uses a switch statement.
>>>
>>> Suggested-by: Christoph Hellwig <hch@lst.de>
>>> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
>>> ---
>>> libxfs/xfs_dir2.c | 36 ++++++++++++++++++++++--------------
>>> libxfs/xfs_dir2.h | 5 ++---
>>> repair/dino_chunks.c | 6 +-----
>>> repair/phase6.c | 2 +-
>>> 4 files changed, 26 insertions(+), 23 deletions(-)
>>>
>>> Eric,
>>>
>>> This is a matching patch to the one that got Reviewed-by Darrick for kernel.
>>>
>>> Tested xfs_repair with the new xfs/348 test with -n ftype=0|1.
>>
>> Thanks, I'll pull this in after Darrick commits it to the kernel.
>>
>
> FYI, commit is in kernel and xfstest xfs/348 which sanity tests
> xfs_repair with this change
> is already merged as well.
Yep, merged & testing now.
Thanks,
-Eric
prev parent reply other threads:[~2017-01-20 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 6:30 [PATCH v3] xfsprogs: replace xfs_mode_to_ftype table with switch statement Amir Goldstein
2017-01-11 16:23 ` Eric Sandeen
2017-01-20 10:58 ` Amir Goldstein
2017-01-20 20:33 ` Eric Sandeen [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=62671831-e226-bcd9-8367-a3cbe3ca1e01@sandeen.net \
--to=sandeen@sandeen.net \
--cc=amir73il@gmail.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--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