From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
nvdimm@lists.linux.dev, linux-fsdevel@vger.kernel.org
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH 0/2] fsdax,xfs: fix warning messages #forregzbot
Date: Wed, 30 Nov 2022 11:30:42 +0100 [thread overview]
Message-ID: <da90b96d-ef1e-4827-b983-15d103a3a1ef@leemhuis.info> (raw)
In-Reply-To: <1669301694-16-1-git-send-email-ruansy.fnst@fujitsu.com>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 24.11.22 15:54, Shiyang Ruan wrote:
> Many testcases failed in dax+reflink mode with warning message in dmesg.
> This also effects dax+noreflink mode if we run the test after a
> dax+reflink test. So, the most urgent thing is solving the warning
> messages.
Darrick in https://lore.kernel.org/all/Y4bZGvP8Ozp+4De%2F@magnolia/
wrote "dax and reflink are totally broken on 6.1". Hence, add this to
the tracking to be sure it's not forgotten.
#regzbot ^introduced 35fcd75af3ed
#regzbot title xfs/dax/reflink are totally broken on 6.1
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
next prev parent reply other threads:[~2022-11-30 10:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 14:54 [PATCH 0/2] fsdax,xfs: fix warning messages Shiyang Ruan
2022-11-24 14:54 ` [PATCH 1/2] fsdax,xfs: fix warning messages at dax_[dis]associate_entry() Shiyang Ruan
2022-11-30 4:08 ` Darrick J. Wong
2022-11-30 8:58 ` Shiyang Ruan
2022-11-30 16:28 ` Darrick J. Wong
2022-11-30 4:12 ` Dan Williams
2022-11-24 14:54 ` [PATCH 2/2] fsdax,xfs: port unshare to fsdax Shiyang Ruan
2022-11-30 3:28 ` Darrick J. Wong
2022-11-27 18:38 ` [PATCH 0/2] fsdax,xfs: fix warning messages Darrick J. Wong
2022-11-28 2:16 ` Shiyang Ruan
2022-11-28 23:08 ` Darrick J. Wong
2022-11-30 3:59 ` Dan Williams
2022-11-30 4:16 ` Darrick J. Wong
2022-11-30 7:05 ` Dan Williams
2022-11-30 21:08 ` Darrick J. Wong
2022-12-01 15:39 ` Shiyang Ruan
2022-12-01 17:47 ` Darrick J. Wong
2022-11-30 21:27 ` Andrew Morton
2022-11-30 21:48 ` Dan Williams
2022-11-30 23:08 ` Darrick J. Wong
2022-11-30 23:58 ` Dan Williams
2022-11-30 10:30 ` Thorsten Leemhuis [this message]
2022-12-12 7:06 ` [PATCH 0/2] fsdax,xfs: fix warning messages #forregzbot Thorsten Leemhuis
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=da90b96d-ef1e-4827-b983-15d103a3a1ef@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=regressions@lists.linux.dev \
/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).