All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-fsdevel@vger.kernel.org
Cc: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
	Jan Kara <jack@suse.cz>, Richard Weinberger <richard@nod.at>,
	Christoph Hellwig <hch@infradead.org>,
	linux-mtd@lists.infradead.org, kernel@pengutronix.de
Subject: UBIFS quota support
Date: Thu, 10 Jan 2019 12:44:48 +0100	[thread overview]
Message-ID: <20190110114448.vcx6w76ibmxwvlh3@pengutronix.de> (raw)

Hi all,

I'm currently working on resurrecting the UBIFS quota patches posted back in
2015 by Dongsheng Yang, last posted here:

http://lists.infradead.org/pipermail/linux-mtd/2015-September/061812.html

First of all I think work stopped there, there is no newer UBIFS quota
support I am missing, right?

One problem with this series was that the quotactl systemcall expects a
path to a block device. UBIFS doesn't work on a block device but on a
character device instead.
The solution in this series was to pass the path to the cdev in
quotactl.  A struct cdev * member was added to struct super_block which
was used to identify the superblock for a given cdev. This approach was
rejected by Christoph ("I don't think the cdev has any business in core
VFS code.").  Apart from that UBIFS can not only be mounted with a path
to the character device (mount -t ubifs /dev/ubix_y /mnt) but also in
the form ubix:volname (mount -t ubifs ubix:volname /mnt) in which case
userspace doesn't have any valid path it could pass in quotactl.

An idea out of this would be to allow to pass the mountpoint instead of
the path to the block device in quotactl which would work with nfs or
even tmpfs aswell. Would that be acceptable? Any other ideas?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-fsdevel@vger.kernel.org
Cc: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
	Jan Kara <jack@suse.cz>,
	linux-mtd@lists.infradead.org,
	Christoph Hellwig <hch@infradead.org>,
	Richard Weinberger <richard@nod.at>,
	kernel@pengutronix.de
Subject: UBIFS quota support
Date: Thu, 10 Jan 2019 12:44:48 +0100	[thread overview]
Message-ID: <20190110114448.vcx6w76ibmxwvlh3@pengutronix.de> (raw)
Message-ID: <20190110114448.oNRoB8ZebFcGJvxxH23Of31NEKdZI6hXrMdrO1ED3kQ@z> (raw)

Hi all,

I'm currently working on resurrecting the UBIFS quota patches posted back in
2015 by Dongsheng Yang, last posted here:

http://lists.infradead.org/pipermail/linux-mtd/2015-September/061812.html

First of all I think work stopped there, there is no newer UBIFS quota
support I am missing, right?

One problem with this series was that the quotactl systemcall expects a
path to a block device. UBIFS doesn't work on a block device but on a
character device instead.
The solution in this series was to pass the path to the cdev in
quotactl.  A struct cdev * member was added to struct super_block which
was used to identify the superblock for a given cdev. This approach was
rejected by Christoph ("I don't think the cdev has any business in core
VFS code.").  Apart from that UBIFS can not only be mounted with a path
to the character device (mount -t ubifs /dev/ubix_y /mnt) but also in
the form ubix:volname (mount -t ubifs ubix:volname /mnt) in which case
userspace doesn't have any valid path it could pass in quotactl.

An idea out of this would be to allow to pass the mountpoint instead of
the path to the block device in quotactl which would work with nfs or
even tmpfs aswell. Would that be acceptable? Any other ideas?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

             reply	other threads:[~2019-01-10 11:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 11:44 Sascha Hauer [this message]
2019-01-10 11:44 ` UBIFS quota support Sascha Hauer
2019-01-22 23:07 ` Richard Weinberger
2019-01-22 23:07   ` Richard Weinberger
2019-01-23  9:43   ` Sascha Hauer
2019-01-23  9:43     ` Sascha Hauer
2019-01-23  9:46     ` Richard Weinberger
2019-01-23  9:46       ` Richard Weinberger
2019-01-23  9:55       ` Sascha Hauer
2019-01-23  9:55         ` Sascha Hauer
2019-01-23 10:47         ` Richard Weinberger
2019-01-23 10:47           ` Richard Weinberger
2019-01-23 15:47   ` Jan Kara
2019-01-23 15:47     ` Jan Kara
2019-01-25  9:21     ` Sascha Hauer
2019-01-25  9:21       ` Sascha Hauer
2019-01-28  8:09       ` Christoph Hellwig
2019-01-28  8:09         ` Christoph Hellwig
2019-01-30 12:45       ` Jan Kara
2019-01-30 12:45         ` Jan Kara
2019-01-31  7:37         ` Sascha Hauer
2019-01-31  7:37           ` Sascha Hauer

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=20190110114448.vcx6w76ibmxwvlh3@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=kernel@pengutronix.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=yangds.fnst@cn.fujitsu.com \
    /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.