All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martin Kepplinger <martink@posteo.de>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	thierry.reding@gmail.com, giedriuswork@gmail.com,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fuse: don't check for file->private_data on open().
Date: Thu, 13 Nov 2014 07:34:58 -0800	[thread overview]
Message-ID: <20141113153458.GB26905@kroah.com> (raw)
In-Reply-To: <0198135B-B7F1-4E40-A9E2-C9D56C421B6F@posteo.de>

On Thu, Nov 13, 2014 at 12:13:32PM +0100, Martin Kepplinger wrote:
> Am 13. November 2014 11:53:29 MEZ, schrieb Miklos Szeredi <miklos@szeredi.hu>:
> >On Thu, Nov 13, 2014 at 11:05 AM, Martin Kepplinger <martink@posteo.de>
> >wrote:
> >
> >> In this week's -next this should have changed. My SSD broke down so i
> >have to delay further work for a few days, i'm sorry.
> >
> >Please be more careful with such patches.  Have you audited all of the
> >(ca. 200) misc drivers?  If not, this might be a good time to do so.
> >If it turns out to be too much, then consider not doing the change.
> >The gain might not be worth the cost.
> >
> >NACK in this form.
> >
> >Thanks,
> >Miklos
> 
> Definitely should have been more careful as I checked fs too late now. I totally unnecessarily broke -next.
> 
> But If fuse-devel is ok with a fix like the one i sent (still has to get tested too) i believe we're covered. I still call for independent review though.

I don't think it's worth it anymore, I'm going to revert the original
patch that caused these problems, as it has the potential to break other
drivers in ways that are not obvious (i.e. not at build time.)

Sorry,

greg k-h

      reply	other threads:[~2014-11-13 15:36 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
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 [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=20141113153458.GB26905@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=giedriuswork@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=miklos@szeredi.hu \
    --cc=thierry.reding@gmail.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 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.