linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	akpm@linux-foundation.org, syzkaller-bugs@googlegroups.com,
	syzbot+01ffaf5d9568dd1609f7@syzkaller.appspotmail.com,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] hfsplus: don't return 0 when fill_super() failed
Date: Sun, 20 May 2018 00:47:33 +0100	[thread overview]
Message-ID: <20180519234733.GW30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180519232503.oya6winh6fvxlh7t@eaf>

On Sat, May 19, 2018 at 08:25:04PM -0300, Ernesto A. Fern�ndez wrote:

> > Oh, I didn't notice that you already wrote that patch.
> > Anyway, whom to ask for merge? Al Viro? Andrew Morton?
> 
> I think Andrew Morton, but only one of my patches for hfsplus has been
> picked up so far, so I can't tell you for sure.
> 
> Al Viro wasn't happy with this patchset and thought it was better to let
> ->put_super() handle the cleanup. I made a second version but I don't
> think he had the time to look at it yet.

Sorry, buried under fs/aio.c review (aio-poll stuff) and assorted shite
around mkdir/open-by-handle right now ;-/  I'll get to that tonight or
tomorrow morning.

  reply	other threads:[~2018-05-19 23:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  2:02 general protection fault in mount_fs syzbot
2018-05-15 10:08 ` [PATCH] hfsplus: don't return 0 when fill_super() failed Tetsuo Handa
     [not found]   ` <20180515164221.57cbosgvu6ahslon@eaf>
     [not found]     ` <201805192255.CAD48427.HLtFMOFVOSOQJF@I-love.SAKURA.ne.jp>
2018-05-19 23:25       ` Ernesto A. Fernández
2018-05-19 23:47         ` Al Viro [this message]
2018-06-21  1:45   ` Ernesto A. Fernández

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=20180519234733.GW30522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=ernesto.mnd.fernandez@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=syzbot+01ffaf5d9568dd1609f7@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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).