All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: odd sillyrename bug in 4.6 / 4.7-rc
Date: Fri, 17 Jun 2016 09:52:02 -0400	[thread overview]
Message-ID: <20160617135202.GA29056@fieldses.org> (raw)
In-Reply-To: <20160617113110.GA8864@infradead.org>

On Fri, Jun 17, 2016 at 04:31:10AM -0700, Christoph Hellwig wrote:
> On Thu, Jun 16, 2016 at 01:29:52PM -0400, J. Bruce Fields wrote:
> > On Thu, Jun 16, 2016 at 08:01:47AM -0700, Christoph Hellwig wrote:
> > > I've run into an odd bug when testing the clone / reflink functionality,
> > > and managed to isolate a testcase not relying on clones.  The issue is
> > > that after a lot of direct I/O hitting ENOSPC on a NFS mount I run
> > > into a silly rename that never gets cleaned up after cleaning up the
> > > directory.
> > 
> > I have a redhat bug for what sounds like the same behavior.  I spent
> > some time looking at it but I don't think I got anywere.
> > 
> > 	https://bugzilla.redhat.com/show_bug.cgi?id=1132610
> > 
> > (But you probably can't see that right now; I'll see if I can open it.)
> 
> I can't see it indeed.

Fixed.  Looking at it, I actually don't think there's much of interest
besides reproducers, which you already have.

--b.

      reply	other threads:[~2016-06-17 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 15:01 odd sillyrename bug in 4.6 / 4.7-rc Christoph Hellwig
2016-06-16 17:29 ` J. Bruce Fields
2016-06-17 11:31   ` Christoph Hellwig
2016-06-17 13:52     ` J. Bruce Fields [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=20160617135202.GA29056@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@infradead.org \
    --cc=linux-nfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.