From: "Darrick J. Wong" <djwong@kernel.org>
To: Ma Xinjian <maxj.fnst@fujitsu.com>
Cc: zlang@redhat.com, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] [PATCH] xfs/348: add _fixed_by tag
Date: Tue, 30 Jul 2024 07:47:51 -0700 [thread overview]
Message-ID: <20240730144751.GB6337@frogsfrogsfrogs> (raw)
In-Reply-To: <20240730075653.3473323-1-maxj.fnst@fujitsu.com>
On Tue, Jul 30, 2024 at 03:56:53PM +0800, Ma Xinjian wrote:
> This test requires a kernel patch since 3bf963a6c6 ("xfs/348: partially revert
> dbcc549317"), so note that in the test.
>
> Signed-off-by: Ma Xinjian <maxj.fnst@fujitsu.com>
> ---
> tests/xfs/348 | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/xfs/348 b/tests/xfs/348
> index 3502605c..e4bc1328 100755
> --- a/tests/xfs/348
> +++ b/tests/xfs/348
> @@ -12,6 +12,9 @@
> . ./common/preamble
> _begin_fstest auto quick fuzzers repair
>
> +_fixed_by_git_commit kernel 38de567906d95 \
> + "xfs: allow symlinks with short remote targets"
Considering that 38de567906d95 is itself a fix for 1eb70f54c445f, do we
want a _broken_by_git_commit to warn people not to apply 1eb70 without
also applying 38de5?
--D
> +
> # Import common functions.
> . ./common/filter
> . ./common/repair
> --
> 2.42.0
>
>
next prev parent reply other threads:[~2024-07-30 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 7:56 [PATCH] [PATCH] xfs/348: add _fixed_by tag Ma Xinjian
2024-07-30 14:47 ` Darrick J. Wong [this message]
2024-07-31 2:58 ` Xinjian Ma (Fujitsu)
2024-08-06 13:19 ` Zorro Lang
2024-08-06 16:14 ` Darrick J. Wong
2024-08-08 8:39 ` Xinjian Ma (Fujitsu)
2024-08-08 15:57 ` Darrick J. Wong
2024-08-09 8:22 ` Xinjian Ma (Fujitsu)
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=20240730144751.GB6337@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=maxj.fnst@fujitsu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.