[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKYAXd-KhOYk_fdKFV-ZbtSeX+Afc65ArnfSVrAqVxL6hMXoCQ@mail.gmail.com>
Date: Wed, 16 Jul 2025 15:59:15 +0900
From: Namjae Jeon <linkinjeon@...nel.org>
To: NeilBrown <neil@...wn.name>
Cc: Steve French <smfrench@...il.com>, Sergey Senozhatsky <senozhatsky@...omium.org>,
Tom Talpey <tom@...pey.com>, Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org,
linux-cifs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] smb/server: various clean-ups
On Wed, Jul 16, 2025 at 2:22 PM NeilBrown <neil@...wn.name> wrote:
>
>
> Hi,
Hi Neil,
> did anyone have a chance to look at these - no replies and they don't
> appear in linux-next ??
Sorry, these patches are not in my mailbox for some reason I don't know...
I guess I missed these ones. I will check and apply the patches now.
Thanks.
>
> Thanks,
> NeilBrown
>
>
> On Mon, 09 Jun 2025, NeilBrown wrote:
> > I am working towards making some changes to how locking is managed for
> > directory operations. Prior to attempting to land these changes I am
> > reviewing code that requests directory operations and cleaning up things
> > that might cause me problems later.
> >
> > These 4 patches are the result of my review of smb/server. Note that
> > patch 3 fixes what appears to be a real deadlock that should be trivial
> > to hit if the client can actually set the flag which, as mentioned in
> > the patch, can trigger the deadlock.
> >
> > Patch 1 is trivial but the others deserve careful review by someone who
> > knows the code. I think they are correct, but I've been wrong before.
> >
> > Thanks,
> > NeilBrown
> >
> > [PATCH 1/4] smb/server: use lookup_one_unlocked()
> > [PATCH 2/4] smb/server: simplify ksmbd_vfs_kern_path_locked()
> > [PATCH 3/4] smb/server: avoid deadlock when linking with
> > [PATCH 4/4] smb/server: add ksmbd_vfs_kern_path()
> >
> >
>
Powered by blists - more mailing lists