From: Breno Leitao <leitao@debian.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Herbert Xu <herbert@gondor.apana.org.au>,
Tejun Heo <tj@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [linux-next:master] [rhashtable] e1d3422c95: xfstests.generic.417.fail
Date: Thu, 16 Jan 2025 01:35:55 -0800 [thread overview]
Message-ID: <20250116-expert-stimulating-chicken-e1ef07@leitao> (raw)
In-Reply-To: <202501161047.39c960cb-lkp@intel.com>
On Thu, Jan 16, 2025 at 01:15:21PM +0800, kernel test robot wrote:
>
> hi, Breno Leitao,
>
> FYI. we noticed this commit is in linux-next/master. now we noticed some
> xfstests tests failed randomly while pass on parent.
>
> xfstests.generic.417 seems have higher rate to fail.
> we also noticed a "Corruption of in-memory data" while running this case.
Thanks for the report. This is a real issue and there is a fix under
review now:
https://lore.kernel.org/all/Z4XWx5X0doetOJni@gondor.apana.org.au/
--breno
prev parent reply other threads:[~2025-01-16 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 5:15 [linux-next:master] [rhashtable] e1d3422c95: xfstests.generic.417.fail kernel test robot
2025-01-16 9:35 ` Breno Leitao [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=20250116-expert-stimulating-chicken-e1ef07@leitao \
--to=leitao@debian.org \
--cc=herbert@gondor.apana.org.au \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=tj@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