[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0001ad7957301981aa1c85e1bdda0f076cbd9a7a.camel@ibm.com>
Date: Wed, 4 Feb 2026 23:04:07 +0000
From: Viacheslav Dubeyko <Slava.Dubeyko@....com>
To: "viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>
CC: "jack@...e.cz" <jack@...e.cz>, "frank.li@...o.com" <frank.li@...o.com>,
"brauner@...nel.org" <brauner@...nel.org>,
"linux-fsdevel@...r.kernel.org"
<linux-fsdevel@...r.kernel.org>,
"slava@...eyko.com" <slava@...eyko.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"shardul.b@...ricsoftware.com" <shardul.b@...ricsoftware.com>,
"shardulsb08@...il.com" <shardulsb08@...il.com>,
"janak@...ricsoftware.com"
<janak@...ricsoftware.com>,
"glaubitz@...sik.fu-berlin.de"
<glaubitz@...sik.fu-berlin.de>,
"syzbot+99f6ed51479b86ac4c41@...kaller.appspotmail.com"
<syzbot+99f6ed51479b86ac4c41@...kaller.appspotmail.com>
Subject: RE: [PATCH v2] hfsplus: fix s_fs_info leak on mount setup failure
On Wed, 2026-02-04 at 18:25 +0000, Al Viro wrote:
> On Wed, Feb 04, 2026 at 05:52:57PM +0000, Al Viro wrote:
> > On Wed, Feb 04, 2026 at 05:40:47PM +0000, Al Viro wrote:
> > > On Wed, Feb 04, 2026 at 05:30:29PM +0000, Al Viro wrote:
> > >
> > > > While we are at it, this
> > > > kfree(sbi->s_vhdr_buf);
> > > > kfree(sbi->s_backup_vhdr_buf);
> > > > might as well go into ->kill_sb(). That would result in the (untested)
> > > > delta below and IMO it's easier to follow that way...
> > >
> > > AFAICS once you've got ->s_root set, you can just return an error and
> > > be done with that - regular cleanup should take care of those parts
> > > (note that iput(NULL) is explicitly a no-op and the same goes for
> > > cancel_delayed_work_sync() on something that has never been through
> > > queue_delayed_work()).
> >
> > Scratch the last one - you'd get nls leak that way, thanks to the
> > trickery in there... Depending on how much do you dislike cleanup.h
> > stuff, there might be a way to deal with that, though...
>
> See viro/vfs.git #untested.hfsplus (I've applied leak fix to your
> #for-next, commits in question are done on top of that).
>
> It builds, but I've done no other testing on it. And nls.h bit
> needs to be discussed on fsdevel, obviously.
OK. Let me spend some time on testing and reviewing the fix.
Thanks,
Slava.
Powered by blists - more mailing lists