fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: fstests@vger.kernel.org
Subject: Re: xfstests generic/484
Date: Mon, 24 Feb 2020 13:45:18 -0800	[thread overview]
Message-ID: <cbb0cc687b1c4509ad891f146b92472fcc1dbb69.camel@kernel.org> (raw)
In-Reply-To: <20200131164619.GA13005@infradead.org>

On Fri, 2020-01-31 at 08:46 -0800, Christoph Hellwig wrote:
> Jeff can you help out with generic/484?
> 
> On Wed, Jan 15, 2020 at 07:00:59AM -0800, Christoph Hellwig wrote:
> > Hi Jeff,
> > 
> > do you remember the story behind xfstests generic/484?  That test has
> > been failing for me ever since it was added and on every file system
> > (which is not surprising given that the functionality isn't file system
> > specific).  Are we expected to fix the issue in the lock ode?  Or did we
> > give up on it?
> ---end quoted text---

Sorry for not seeing this before. I blame gmail.

I didn't actually add this test. I believe Eryu may have added it in
response to a bug report and an initial patch that I proposed that
turned out not to be the right approach.

I'm fine with removing this test. We may eventually want to fix this,
but it probably will mean reworking how the file table gets inherited
across execve (which is outside my usual wheelhouse).

-- 
Jeff Layton <jlayton@kernel.org>


      reply	other threads:[~2020-02-24 21:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 15:00 xfstests generic/484 Christoph Hellwig
2020-01-31 16:46 ` Christoph Hellwig
2020-02-24 21:45   ` Jeff Layton [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=cbb0cc687b1c4509ad891f146b92472fcc1dbb69.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).