From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: "Darrick J. Wong" <djwong@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Cc: amir73il@gmail.com, dchinner@redhat.com, yangx.jy@fujitsu.com,
linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.10 0/2] Fix xfs/179 for 5.10 stable
Date: Mon, 7 Aug 2023 10:39:44 +0800 [thread overview]
Message-ID: <5d44e45b-cb85-b878-f21d-d0b508c3b696@linux.dev> (raw)
In-Reply-To: <20230804154757.GI11352@frogsfrogsfrogs>
On 8/4/23 23:47, Darrick J. Wong wrote:
> On Thu, Aug 03, 2023 at 05:36:50PM +0800, Guoqing Jiang wrote:
>> Hi,
>>
>> With the two patches applied, xfs/179 can pass in 5.10.188. Otherwise I got
>>
>> [root@localhost xfstests]# ./check xfs/179
>> FSTYP -- xfs (non-debug)
>> PLATFORM -- Linux/x86_64 localhost 5.10.188-default #14 SMP Thu Aug 3 15:23:19 CST 2023
>> MKFS_OPTIONS -- -f /dev/loop1
>> MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0 /dev/loop1 /mnt/scratch
>>
>> xfs/179 1s ... [failed, exit status 1]- output mismatch (see /root/xfstests/results//xfs/179.out.bad)
>> --- tests/xfs/179.out 2023-07-13 16:12:27.000000000 +0800
>> +++ /root/xfstests/results//xfs/179.out.bad 2023-08-03 16:55:38.173787911 +0800
>> @@ -8,3 +8,5 @@
>> Check scratch fs
>> Remove reflinked files
>> Check scratch fs
>> +xfs_repair fails
>> +(see /root/xfstests/results//xfs/179.full for details)
>> ...
>> (Run 'diff -u /root/xfstests/tests/xfs/179.out /root/xfstests/results//xfs/179.out.bad' to see the entire diff)
>>
>> HINT: You _MAY_ be missing kernel fix:
>> b25d1984aa88 xfs: estimate post-merge refcounts correctly
>>
>> Ran: xfs/179
>> Failures: xfs/179
>> Failed 1 of 1 tests
>>
>> Please review if they are approriate for 5.10 stable.
> Seems fine to me, but ... there is no maintainer for 5.10; is your
> employer willing to support this LTS kernel?
Hi Darrick,
Thanks for your review! I think Amir is the maintainer for 5.10 😉. I
can help
if needed since our kernel is heavily based on 5.10 stable. We also run
tests
against 5.10 stable, that is why I send fixes patches for it.
Hi Greg,
Could you consider add the two to your list? Thank you!
Regards,
Guoqing
next prev parent reply other threads:[~2023-08-07 2:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 9:36 [PATCH 5.10 0/2] Fix xfs/179 for 5.10 stable Guoqing Jiang
2023-08-03 9:36 ` [PATCH 5.10 1/2] xfs: hoist refcount record merge predicates Guoqing Jiang
2023-08-03 9:36 ` [PATCH 5.10 2/2] xfs: estimate post-merge refcounts correctly Guoqing Jiang
2023-08-04 15:47 ` [PATCH 5.10 0/2] Fix xfs/179 for 5.10 stable Darrick J. Wong
2023-08-07 2:39 ` Guoqing Jiang [this message]
2023-08-07 9:11 ` Greg KH
2023-08-07 14:00 ` Guoqing Jiang
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=5d44e45b-cb85-b878-f21d-d0b508c3b696@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=amir73il@gmail.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yangx.jy@fujitsu.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