[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKFNMonVb6s3Cey5riXFwd+C3wy87fHbMUtnq3SXooXgsSD5yA@mail.gmail.com>
Date: Tue, 16 Aug 2022 18:18:18 +0900
From: Ryusuke Konishi <konishi.ryusuke@...il.com>
To: Dongliang Mu <mudongliangabcd@...il.com>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-nilfs <linux-nilfs@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Jiacheng Xu <stitch@....edu.cn>
Subject: Re: [PATCH] nilfs2: fix use-after-free bug in nilfs_mdt_destroy()
On Tue, Aug 16, 2022 at 12:25 PM Dongliang Mu wrote:
> > Dongliang (or Jiacheng?), would it be possible for you to post a revised patch
> > against inode_init_always() that moves the call of security_inode_alloc()
> > instead of i_private initialization (as Al Viro said in a nearby thread [1]) ?
> > If you have time, I would like to leave it to you since you wrote the
> > original patch for inode_init_always().
>
> Sure, I will post a v2 patch that moves security_inode_alloc to the
> location just prior to
> this_cpu_inc(nr_inodes);
> with proper commit message.
>
I saw you already sent the v2 patch on linux-fsdevel, etc.
Just thank you for your quick follow.
Regards,
Ryusuke Konishi
> >
> > [1] https://lkml.kernel.org/r/CAO4S-mficMz1mQW06EuCF+o11+mRDiCpufqVfoHkcRbQbs8kVw@mail.gmail.com
> >
> > Thanks,
> > Ryusuke Konishi
Powered by blists - more mailing lists