linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.cz>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs: misc/016 hangs at ioctl
Date: Wed, 4 Dec 2019 17:29:54 +0100	[thread overview]
Message-ID: <20191204162954.GF2734@twin.jikos.cz> (raw)
In-Reply-To: <20191204161723.GE2734@twin.jikos.cz>

On Wed, Dec 04, 2019 at 05:17:23PM +0100, David Sterba wrote:
> On Wed, Dec 04, 2019 at 02:08:14PM +0800, Qu Wenruo wrote:
> > On 2019/12/4 下午2:06, Qu Wenruo wrote:
> > > Found a strange failure at btrfs-progs selftest misc/016.
> > > 
> > > It hangs at current master 63de37476ebd ("Merge tag
> > > 'tag-chrome-platform-for-v5.5' of
> > > git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux").
> > > 
> > > What makes it even more mysterious is, misc-5.5 passes.
> > > 
> > > Since there is no other btrfs pull, it's caused by some upstream
> > > non-btrfs commits.
> > 
> > BTW, no blocked kernel thread, no CPU usage.
> > 
> > And the hang can be canceled with a signal.
> > 
> > > 
> > > Doing bisecting, but any clue will be appreciated.
> 
> This looks like a problem caused by recent merge of updates to pipe
> (commit 6a965666b7e7475c2f8c8e724703db58b8a8a445). I can reproduce that
> and now building test kernel before that commit. As this also blocks all
> fstests that use send, we have to wait until it's fixed in master
> branch.

That hangs too, so that's going to be a long bisect.

  reply	other threads:[~2019-12-04 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04  6:06 btrfs-progs: misc/016 hangs at ioctl Qu Wenruo
2019-12-04  6:08 ` Qu Wenruo
2019-12-04 16:17   ` David Sterba
2019-12-04 16:29     ` David Sterba [this message]
2019-12-04 17:06       ` David Sterba
2019-12-09 15:32 ` David Sterba

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=20191204162954.GF2734@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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).