fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Murphy Zhou <jencce.kernel@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic: require fibmap for testcases using filefrag
Date: Fri, 17 Jan 2020 00:45:17 -0800	[thread overview]
Message-ID: <20200117084517.GA24082@infradead.org> (raw)
In-Reply-To: <20200117083824.32450-1-jencce.kernel@gmail.com>

On Fri, Jan 17, 2020 at 04:38:24PM +0800, Murphy Zhou wrote:
> To mute false alarm on NFS, which is reporting FIBMAP unsupported.

How do these tests end up using FIBMAP?  We really should not use FIBMAP
in any tests except those exercising FIBMAP itself.


  reply	other threads:[~2020-01-17  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17  8:38 [PATCH] generic: require fibmap for testcases using filefrag Murphy Zhou
2020-01-17  8:45 ` Christoph Hellwig [this message]
2020-01-17 10:02   ` Murphy Zhou
2020-01-18  0:47     ` Darrick J. Wong
2020-01-18  9:38       ` Murphy Zhou
2020-01-19 22:02         ` Christoph Hellwig
2020-01-22 10:22           ` Murphy Zhou

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=20200117084517.GA24082@infradead.org \
    --to=hch@infradead.org \
    --cc=fstests@vger.kernel.org \
    --cc=jencce.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).