From: Al Viro <viro@zeniv.linux.org.uk>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH 4/5] ksmbd: don't open-code %pf
Date: Sat, 20 Aug 2022 16:33:31 +0100 [thread overview]
Message-ID: <YwD+y2cXpcenIHlW@ZenIV> (raw)
In-Reply-To: <CAKYAXd9DGgLJ=-hcdADXVZUqp2aYRkGr2YKpfUND6S_GuaWgWQ@mail.gmail.com>
On Sat, Aug 20, 2022 at 02:44:29PM +0900, Namjae Jeon wrote:
> > OK... FWIW, I've another ksmbd patch hanging around and it might be
> > less PITA if I put it + those two patches into never-rebased branch
> > (for-ksmbd) for ksmbd folks to pull from. Fewer pointless conflicts
> > that way...
> Okay, Thanks for this. I'm trying to resend "ksmbd: fix racy issue
> from using ->d_parent and ->d_name" patch to you, but It conflict with
> these patches:)
> We will pull them from that branch if you create it.
OK, pull request follows:
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-ksmbd
for you to fetch changes up to f2ea6d96500dd8947467f774d70700c1ba3ed8ef:
ksmbd: constify struct path (2022-08-20 10:54:48 -0400)
----------------------------------------------------------------
assorted ksmbd cleanups
Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (3):
ksmbd: don't open-code file_path()
ksmbd: don't open-code %pD
ksmbd: constify struct path
fs/ksmbd/misc.c | 2 +-
fs/ksmbd/misc.h | 2 +-
fs/ksmbd/smb2pdu.c | 33 ++++++++++++++++-----------------
fs/ksmbd/smbacl.c | 6 +++---
fs/ksmbd/smbacl.h | 6 +++---
fs/ksmbd/vfs.c | 18 ++++++++----------
fs/ksmbd/vfs.h | 2 +-
7 files changed, 33 insertions(+), 36 deletions(-)
next prev parent reply other threads:[~2022-08-20 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:57 [PATCH 1/5] dynamic_dname(): drop unused dentry argument Al Viro
2022-08-18 2:58 ` [PATCH 2/5] ksmbd: don't open-code file_path() Al Viro
2022-08-18 6:19 ` Namjae Jeon
2022-08-18 2:58 ` [PATCH 3/5] ->getprocattr(): attribute name is const char *, TYVM Al Viro
2022-08-18 18:34 ` Schaufler, Casey
2022-08-26 7:45 ` Christian Brauner
2022-08-18 2:59 ` [PATCH 4/5] ksmbd: don't open-code %pf Al Viro
2022-08-18 6:08 ` Namjae Jeon
2022-08-18 20:35 ` Al Viro
2022-08-18 23:26 ` Namjae Jeon
2022-08-20 3:47 ` Al Viro
2022-08-20 5:44 ` Namjae Jeon
2022-08-20 15:33 ` Al Viro [this message]
2022-08-21 2:06 ` Steve French
2022-08-18 2:59 ` [PATCH 5/5] d_path.c: typo fix Al Viro
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=YwD+y2cXpcenIHlW@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).