FSTests Archive on lore.kernel.org
 help / color / Atom feed
* xfstests generic/484
@ 2020-01-15 15:00 Christoph Hellwig
  2020-01-31 16:46 ` Christoph Hellwig
  0 siblings, 1 reply; 3+ messages in thread
From: Christoph Hellwig @ 2020-01-15 15:00 UTC (permalink / raw)
  To: jlayton; +Cc: fstests

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?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: xfstests generic/484
  2020-01-15 15:00 xfstests generic/484 Christoph Hellwig
@ 2020-01-31 16:46 ` Christoph Hellwig
  2020-02-24 21:45   ` Jeff Layton
  0 siblings, 1 reply; 3+ messages in thread
From: Christoph Hellwig @ 2020-01-31 16:46 UTC (permalink / raw)
  To: jlayton; +Cc: fstests

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---

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: xfstests generic/484
  2020-01-31 16:46 ` Christoph Hellwig
@ 2020-02-24 21:45   ` Jeff Layton
  0 siblings, 0 replies; 3+ messages in thread
From: Jeff Layton @ 2020-02-24 21:45 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: fstests

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>


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-15 15:00 xfstests generic/484 Christoph Hellwig
2020-01-31 16:46 ` Christoph Hellwig
2020-02-24 21:45   ` Jeff Layton

FSTests Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/fstests/0 fstests/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 fstests fstests/ https://lore.kernel.org/fstests \
		fstests@vger.kernel.org
	public-inbox-index fstests

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.fstests


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git