From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [xfs] 27d1053021: xfstests.xfs.173.fail
Date: Thu, 19 Sep 2019 23:56:25 +0200 [thread overview]
Message-ID: <20190919215625.GA13358@lst.de> (raw)
In-Reply-To: <20190919174705.GA9622@lst.de>
On Thu, Sep 19, 2019 at 07:47:05PM +0200, Christoph Hellwig wrote:
> On Thu, Sep 19, 2019 at 09:46:02AM +0800, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: 27d10530217ee6d6a0388014fd773820ee354ce5 ("xfs: remove the unused XFS_ALLOC_USERDATA flag")
>
> Well, this does not make a whole lot of sense, given that the patch
> literally just removes an unused flag. that being said that test has
> been father flakey for me for a long time.
But the weird part is that it actually reproduces here with 1k block
size file system despite make no sense at all..
prev parent reply other threads:[~2019-09-19 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 1:46 [xfs] 27d1053021: xfstests.xfs.173.fail kernel test robot
2019-09-19 17:47 ` Christoph Hellwig
2019-09-19 21:56 ` Christoph Hellwig [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=20190919215625.GA13358@lst.de \
--to=hch@lst.de \
--cc=darrick.wong@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=rong.a.chen@intel.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