From: Jan Kara <jack@suse.cz>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org,
Jan Kara <jack@suse.com>, Richard Weinberger <richard@nod.at>,
kernel@pengutronix.de
Subject: Re: [PATCH 1/8] quota: Allow to pass mount path to quotactl
Date: Mon, 27 Jan 2020 11:45:18 +0100 [thread overview]
Message-ID: <20200127104518.GC19414@quack2.suse.cz> (raw)
In-Reply-To: <20200124131323.23885-2-s.hauer@pengutronix.de>
On Fri 24-01-20 14:13:16, Sascha Hauer wrote:
> This patch introduces the Q_PATH flag to the quotactl cmd argument.
> When given, the path given in the special argument to quotactl will
> be the mount path where the filesystem is mounted, instead of a path
> to the block device.
> This is necessary for filesystems which do not have a block device as
> backing store. Particularly this is done for upcoming UBIFS support.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Thanks for the patch. Some comments are below.
> @@ -821,15 +822,20 @@ int kernel_quotactl(unsigned int cmd, const char __user *special,
> {
> uint cmds, type;
> struct super_block *sb = NULL;
> - struct path path, *pathp = NULL;
> + struct path file_path, *file_pathp = NULL, sb_path;
> int ret;
> + bool q_path;
>
> cmds = cmd >> SUBCMDSHIFT;
> type = cmd & SUBCMDMASK;
>
> +
Unnecessary empty line added...
> if (type >= MAXQUOTAS)
> return -EINVAL;
>
> + q_path = cmds & Q_PATH;
> + cmds &= ~Q_PATH;
> +
> /*
> * As a special case Q_SYNC can be called without a specific device.
> * It will iterate all superblocks that have quota enabled and call
> @@ -847,28 +853,45 @@ int kernel_quotactl(unsigned int cmd, const char __user *special,
> * resolution (think about autofs) and thus deadlocks could arise.
> */
> if (cmds == Q_QUOTAON) {
> - ret = user_path_at(AT_FDCWD, addr, LOOKUP_FOLLOW|LOOKUP_AUTOMOUNT, &path);
> + ret = user_path_at(AT_FDCWD, addr,
> + LOOKUP_FOLLOW | LOOKUP_AUTOMOUNT,
> + &file_path);
> if (ret)
> - pathp = ERR_PTR(ret);
> + file_pathp = ERR_PTR(ret);
> else
> - pathp = &path;
> + file_pathp = &file_path;
> }
>
> - sb = quotactl_block(special, cmds);
> - if (IS_ERR(sb)) {
> - ret = PTR_ERR(sb);
> - goto out;
> + if (q_path) {
> + ret = user_path_at(AT_FDCWD, special,
> + LOOKUP_FOLLOW | LOOKUP_AUTOMOUNT,
> + &sb_path);
> + if (ret)
> + goto out;
> +
> + sb = sb_path.mnt->mnt_sb;
So I've realized that just looking up superblock with user_path_at() is not
enough. Quota code also expects that the superblock will be locked
(sb->s_umount) and filesystem will not be frozen (in case the quota
operation is going to modify the filesystem). This is needed to serialize
e.g. remount and quota operations or quota operations among themselves.
So you still need something like following to get superblock from the path:
static int quotactl_path(const char __user *special, int cmd, struct path *path)
{
struct super_block *sb;
ret = user_path_at(AT_FDCWD, special, LOOKUP_FOLLOW | LOOKUP_AUTOMOUNT,
path);
if (ret)
return ret;
sb = sb_path.mnt->mnt_sb;
restart:
if (quotactl_cmd_onoff(cmd))
down_write(&sb->s_umount);
else
down_read(&sb->s_umount);
if (quotactl_cmd_write(cmd) && sb->s_writers.frozen != SB_UNFROZEN) {
if (quotactl_cmd_onoff(cmd))
up_write(&sb->s_umount);
else
up_read(&sb->s_umount);
wait_event(sb->s_writers.wait_unfrozen,
sb->s_writers.frozen == SB_UNFROZEN);
goto restart;
}
return sb;
}
And then appropriate counterparts when releasing the superblock.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-01-27 10:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 13:13 [PATCH v4 0/8] Add quota support to UBIFS Sascha Hauer
2020-01-24 13:13 ` [PATCH 1/8] quota: Allow to pass mount path to quotactl Sascha Hauer
2020-01-27 10:45 ` Jan Kara [this message]
2020-01-28 10:06 ` Sascha Hauer
2020-01-28 11:41 ` Jan Kara
2020-01-29 1:29 ` Al Viro
2020-01-29 16:14 ` Jan Kara
2020-02-04 10:35 ` Sascha Hauer
2020-02-18 9:22 ` Jan Kara
2020-01-24 13:13 ` [PATCH 2/8] ubifs: move checks and preparation into setflags() Sascha Hauer
2020-01-24 13:13 ` [PATCH 3/8] ubifs: Add support for FS_IOC_FS[SG]ETXATTR ioctls Sascha Hauer
2020-01-24 13:13 ` [PATCH 4/8] ubifs: do not ubifs_inode() on potentially NULL pointer Sascha Hauer
2020-01-24 13:13 ` [PATCH 5/8] ubifs: Factor out ubifs_set_feature_flag() Sascha Hauer
2020-01-24 13:13 ` [PATCH 6/8] ubifs: Add support for project id Sascha Hauer
2020-01-24 13:13 ` [PATCH 7/8] ubifs: export get_znode Sascha Hauer
2020-01-24 13:13 ` [PATCH 8/8] ubifs: Add quota support Sascha Hauer
2020-01-26 18:30 ` kbuild test robot
2020-01-26 18:30 ` [RFC PATCH] ubifs: tnc_next() can be static kbuild test robot
2021-01-22 15:15 [PATCH v5 0/8] Add quota support to UBIFS Sascha Hauer
2021-01-22 15:15 ` [PATCH 1/8] quota: Allow to pass mount path to quotactl Sascha Hauer
2021-01-22 17:16 ` Christoph Hellwig
2021-01-25 8:38 ` Sascha Hauer
2021-01-25 15:45 ` Jan Kara
2021-01-25 20:42 ` Christoph Hellwig
2021-01-26 13:17 ` Jan Kara
2021-01-26 13:34 ` Christoph Hellwig
2021-01-26 16:18 ` Jan Kara
2021-01-27 14:05 ` Sascha Hauer
2021-01-27 14:19 ` Jan Kara
2021-01-26 10:45 ` Sascha Hauer
2021-01-27 14:46 ` Jan Kara
2021-01-27 16:25 ` Christoph Hellwig
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=20200127104518.GC19414@quack2.suse.cz \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=kernel@pengutronix.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
/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).