From: Giedrius Statkevicius <giedriuswork@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: martink@posteo.de, linux-kernel@vger.kernel.org
Subject: Re: [Bisected] Regression: cpu stuck in gvfsd-fuse, can't shutdown
Date: Tue, 11 Nov 2014 23:44:26 +0200 [thread overview]
Message-ID: <5462833A.5050706@gmail.com> (raw)
In-Reply-To: <20141111210506.GA26119@kroah.com>
On 2014.11.11 23:05, Greg KH wrote:
>
> If you revert this patch, does things go back to "normal" for you?
Originally I've only tested where the HEAD was
32eca22180804f71b06b63fd29b72f58be8b3c47 versus
32eca22180804f71b06b63fd29b72f58be8b3c47~1 but now I recompiled and
tested a vanilla 3.18.0-rc4-next-20141111 on which this issue occurs and
then tried a version with that particular patch reverted and then no
lockups happen.
next prev parent reply other threads:[~2014-11-11 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 20:27 [Bisected] Regression: cpu stuck in gvfsd-fuse, can't shutdown Giedrius Statkevicius
2014-11-11 21:05 ` Greg KH
2014-11-11 21:44 ` Giedrius Statkevicius [this message]
2014-11-12 11:26 ` Thierry Reding
2014-11-12 16:31 ` [PATCH] fuse: don't check for file->private_data on open() Martin Kepplinger
2014-11-12 16:41 ` Martin Kepplinger
2014-11-12 17:23 ` Giedrius Statkevicius
2014-11-12 18:56 ` [PATCH] fuse: Don't check for file->private_data on open(). It is set by the core Martin Kepplinger
2014-11-13 9:40 ` [PATCH] fuse: don't check for file->private_data on open() Miklos Szeredi
2014-11-13 10:05 ` Martin Kepplinger
2014-11-13 10:53 ` Miklos Szeredi
2014-11-13 11:13 ` Martin Kepplinger
2014-11-13 15:34 ` Greg Kroah-Hartman
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=5462833A.5050706@gmail.com \
--to=giedriuswork@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
/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).