From: Hans de Goede <hdegoede@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Hans de Goede <hdegoede@redhat.com>,
David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH resend 0/4] vboxsf: Add support for the atomic_open directory-inode op
Date: Mon, 1 Mar 2021 19:41:39 +0100 [thread overview]
Message-ID: <20210301184143.29878-1-hdegoede@redhat.com> (raw)
Hi Al,
Here is a resend of my patch series to add support for the atomic_open
directory-inode op to vboxsf, since this series seems to have fallen
through the cracks.
Note this is not just an enhancement this also fixes an actual issue
which users are hitting, see the commit message of patch 4/4.
Regards,
Hans
Hans de Goede (4):
vboxsf: Honor excl flag to the dir-inode create op
vboxsf: Make vboxsf_dir_create() return the handle for the created
file
vboxsf: Add vboxsf_[create|release]_sf_handle() helpers
vboxsf: Add support for the atomic_open directory-inode op
fs/vboxsf/dir.c | 76 +++++++++++++++++++++++++++++++++++++++-------
fs/vboxsf/file.c | 71 +++++++++++++++++++++++++++----------------
fs/vboxsf/vfsmod.h | 7 +++++
3 files changed, 116 insertions(+), 38 deletions(-)
--
2.30.1
next reply other threads:[~2021-03-01 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 18:41 Hans de Goede [this message]
2021-03-01 18:41 ` [PATCH resend 1/4] vboxsf: Honor excl flag to the dir-inode create op Hans de Goede
2021-03-01 18:41 ` [PATCH resend 2/4] vboxsf: Make vboxsf_dir_create() return the handle for the created file Hans de Goede
2021-03-01 18:41 ` [PATCH resend 3/4] vboxsf: Add vboxsf_[create|release]_sf_handle() helpers Hans de Goede
2021-03-01 18:41 ` [PATCH resend 4/4] vboxsf: Add support for the atomic_open directory-inode op Hans de Goede
2021-03-31 11:38 ` [PATCH resend 0/4] " 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=20210301184143.29878-1-hdegoede@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 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.