linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
	David Howells <dhowells@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: [PATCH v12 resend 0/1] fs: Add VirtualBox guest shared folder (vboxsf)
Date: Sun, 11 Aug 2019 15:38:51 +0200	[thread overview]
Message-ID: <20190811133852.5173-1-hdegoede@redhat.com> (raw)

Hello Everyone,

Here is a resend of the 12th version of my cleaned-up / refactored version
of the VirtualBox shared-folder VFS driver. It seems that for some reason
only the cover letter of my initial-posting of v12 has made it to the list.

This version hopefully addresses all issues pointed out in David Howell's
review of v11 (thank you for the review David):

Changes in v12:
-Move make_kuid / make_kgid calls to option parsing time and add
 uid_valid / gid_valid checks.
-In init_fs_context call current_uid_gid() to init uid and gid
-Validate dmode, fmode, dmask and fmask options during option parsing
-Use correct types for various mount option variables (kuid_t, kgid_t, umode_t)
-Some small coding-style tweaks

For changes in older versions see the change log in the patch.

This version has been used by several distributions (arch, Fedora) for a
while now, so hopefully we can get this upstream soonish, please review.

Regards,

Hans


             reply	other threads:[~2019-08-11 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 13:38 Hans de Goede [this message]
2019-08-11 15:07 ` [PATCH v12 resend 0/1] fs: Add VirtualBox guest shared folder (vboxsf) Randy Dunlap
2019-08-11 15:09   ` Hans de Goede
2019-08-11 15:16     ` Randy Dunlap
2019-08-11 15:31       ` Randy Dunlap
2019-08-11 16:01         ` Randy Dunlap
2019-08-11 16:34         ` Hans de Goede
2019-08-11 15:39       ` Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2019-08-11 16:31 Hans de Goede

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=20190811133852.5173-1-hdegoede@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dhowells@redhat.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 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).