All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org,
	Kent Overstreet <kent.overstreet@gmail.com>
Subject: [PATCH] fs: export getname()
Date: Thu, 16 Nov 2023 16:18:22 -0500	[thread overview]
Message-ID: <20231116211822.leztxrldjzyqadtm@moria.home.lan> (raw)
In-Reply-To: <20231116050832.GX1957730@ZenIV>

On Thu, Nov 16, 2023 at 05:08:32AM +0000, Al Viro wrote:
> (in #work.namei; used for bcachefs locking fix)
> From 74d016ecc1a7974664e98d1afbf649cd4e0e0423 Mon Sep 17 00:00:00 2001
> From: Al Viro <viro@zeniv.linux.org.uk>
> Date: Wed, 15 Nov 2023 22:41:27 -0500
> Subject: [PATCH 1/2] new helper: user_path_locked_at()
> 
> Equivalent of kern_path_locked() taking dfd/userland name.
> User introduced in the next commit.

also applying this:
-- >8 --

The locking fix in bch2_ioctl_subvolume_destroy() also needs getname()
exported; previous patch provided filename_path_locked()

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>

diff --git a/fs/namei.c b/fs/namei.c
index eab372e04767..83dd8b51995a 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -218,6 +218,7 @@ getname(const char __user * filename)
 {
 	return getname_flags(filename, 0, NULL);
 }
+EXPORT_SYMBOL(getname);
 
 struct filename *
 getname_kernel(const char * filename)

  parent reply	other threads:[~2023-11-16 21:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16  5:08 [PATCH 1/2] new helper: user_path_locked_at() Al Viro
2023-11-16  5:09 ` [PATCH 2/2] bch2_ioctl_subvolume_destroy(): fix locking Al Viro
2023-11-16  5:10 ` [PATCH 1/2] new helper: user_path_locked_at() Al Viro
2023-11-16 21:18 ` Kent Overstreet [this message]
2023-11-16 21:53   ` [PATCH] fs: export getname() Al Viro
2023-11-16 21:56     ` Kent Overstreet

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=20231116211822.leztxrldjzyqadtm@moria.home.lan \
    --to=kent.overstreet@linux.dev \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.