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>
Cc: David Howells <dhowells@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v13] fs: Add VirtualBox guest shared folder (vboxsf) support
Date: Thu, 15 Aug 2019 15:33:31 +0200	[thread overview]
Message-ID: <da593279-4765-09c8-0594-3e9b4cbec3a1@redhat.com> (raw)
In-Reply-To: <20190815131253.237921-1-hdegoede@redhat.com>

Hi,

On 15-08-19 15:12, Hans de Goede wrote:
> Hello Everyone,
> 
> Here is the 13th version of my cleaned-up / refactored version of the
> VirtualBox shared-folder VFS driver.
> 
> This version hopefully addresses all issues pointed out in Christoph's
> review of v12 (thank you for the review Christoph):
> 
> Changes in v13:
> - Add SPDX tag to Makefile, use foo-y := to set objectfile list
> - Drop kerneldoc headers stating the obvious from vfs callbacks,
>    to avoid them going stale
> - Replace sf_ prefix of functions and data-types with vboxsf_
> - Use more normal naming scheme for sbi and private inode data:
>      struct vboxsf_sbi *sbi = VBOXSF_SBI(inode->i_sb);
>      struct vboxsf_inode *sf_i = VBOXSF_I(inode);
> - Refactor directory reading code
> - Use goto based unwinding instead of nested if-s in a number of places
> - Consolidate dir unlink and rmdir inode_operations into a single function
> - Use the page-cache for regular reads/writes too
> - Directly set super_operations.free_inode to what used to be our
>    vboxsf_i_callback, instead of setting super_operations.destroy_inode
>    to a function which just does: call_rcu(&inode->i_rcu, vboxsf_i_callback);
> - Use spinlock_irqsafe for ino_idr_lock
>    vboxsf_free_inode may be called from a RCU callback, and thus from
>    softirq context, so we need to use spinlock_irqsafe vboxsf_new_inode.
>    On alloc_inode failure vboxsf_free_inode may be called from process
>    context, so it too needs to use spinlock_irqsafe.
> 
> This version has been used by several distributions (arch, Fedora) for a
> while now, so hopefully we can get this upstream soonish, please review.

I just noticed I forgot to add 0/1 to the subject of this cover letter,
the second mail with the same subject (sorry) is the actual patch.

Regards,

Hans

      parent reply	other threads:[~2019-08-15 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 13:12 [PATCH v13] fs: Add VirtualBox guest shared folder (vboxsf) support Hans de Goede
2019-08-15 13:12 ` Hans de Goede
2019-08-16  7:56   ` Christoph Hellwig
2019-08-16  9:01     ` Hans de Goede
2019-08-16  9:39       ` Hans de Goede
2019-08-16 12:49       ` Christoph Hellwig
2019-08-15 13:33 ` Hans de Goede [this message]

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=da593279-4765-09c8-0594-3e9b4cbec3a1@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --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).