mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: viro@zeniv.linux.org.uk, torvalds@linux-foundation.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	hch@infradead.org
Cc: tglx@linutronix.de, kstewart@linuxfoundation.org,
	gregkh@linuxfoundation.org, pombredanne@nexb.com,
	Christian Brauner <christian.brauner@ubuntu.com>
Subject: [PATCH 0/6 resend] statfs: handle mount propagation
Date: Wed,  2 May 2018 17:42:33 +0200	[thread overview]
Message-ID: <20180502154239.14013-1-christian.brauner@ubuntu.com> (raw)

Hey,

This is the second resend of this patchset. I'm not sure whether it has
simply been overlooked but the number of people get_maintainer.pl was
rather small and seemed a little random so I added Linus and Christoph,
two people I know that do look at VFS stuff at least from time to time,
although they weren't listed by get_maintainer.pl. I hope that's ok.

This little series
- unifies the definition of constants in statfs.h and fs.h
  *Note, that Andreas has expressed doubts whether this unification is
  useful. Please see https://lkml.org/lkml/2018/4/13/571 . I still think
  it is but I'm happy to drop these two patches if others agree.*
- extends statfs to handle mount propagation. This will let userspace
  easily query a given mountpoint for MS_UNBINDABLE, MS_SHARED,
  MS_PRIVATE and MS_SLAVE without always having to do costly parsing of
  /proc/<pid>/mountinfo.
  To this end the flags:
  - ST_UNBINDABLE
  - ST_SHARED
  - ST_PRIVATE
  - ST_SLAVE
  are added. They have the same value as their MS_* counterparts.

Thanks!
Christian

Christian Brauner (6):
  fs: use << for MS_* flags
  statfs: use << to align with fs header
  statfs: add ST_UNBINDABLE
  statfs: add ST_SHARED
  statfs: add ST_SLAVE
  statfs: add ST_PRIVATE

 fs/statfs.c             | 16 +++++++++++++++-
 include/linux/statfs.h  | 30 +++++++++++++++++-------------
 include/uapi/linux/fs.h | 33 +++++++++++++++++----------------
 3 files changed, 49 insertions(+), 30 deletions(-)

-- 
2.17.0

             reply	other threads:[~2018-05-02 15:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 15:42 Christian Brauner [this message]
2018-05-02 15:42 ` [PATCH 1/6 resend] fs: use << for MS_* flags Christian Brauner
2018-05-02 15:42 ` [PATCH 2/6 resend] statfs: use << to align with fs header Christian Brauner
2018-05-02 15:42 ` [PATCH 3/6 resend] statfs: add ST_UNBINDABLE Christian Brauner
2018-05-02 15:42 ` [PATCH 4/6 resend] statfs: add ST_SHARED Christian Brauner
2018-05-02 15:42 ` [PATCH 5/6 resend] statfs: add ST_SLAVE Christian Brauner
2018-05-03  2:36   ` Linus Torvalds
2018-05-03 13:17     ` Christian Brauner
2018-05-02 15:42 ` [PATCH 6/6 resend] statfs: add ST_PRIVATE Christian Brauner
2018-05-02 16:09 ` [PATCH 0/6 resend] statfs: handle mount propagation Al Viro
2018-05-03 13:04   ` Christian Brauner
2018-05-03 13:43     ` Al Viro
2018-05-03 13:57       ` Christian Brauner
  -- strict thread matches above, loose matches on Subject: below --
2018-04-18  9:27 [PATCH 0/6 RESEND] " Christian Brauner

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=20180502154239.14013-1-christian.brauner@ubuntu.com \
    --to=christian.brauner@ubuntu.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®