From: Hans de Goede <hdegoede@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v12 resend 0/1] fs: Add VirtualBox guest shared folder (vboxsf)
Date: Sun, 11 Aug 2019 18:34:55 +0200 [thread overview]
Message-ID: <4ba48f60-10f7-95dc-d259-68c6e3d4d026@redhat.com> (raw)
In-Reply-To: <69c4d47d-2b33-72e9-9da0-7a251070cf6c@infradead.org>
Hi,
On 8/11/19 5:31 PM, Randy Dunlap wrote:
> On 8/11/19 8:16 AM, Randy Dunlap wrote:
>> On 8/11/19 8:09 AM, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 8/11/19 5:07 PM, Randy Dunlap wrote:
>>>> On 8/11/19 6:38 AM, Hans de Goede wrote:
>>>>> 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.
>>>>
>>>> Hi,
>>>> Still looks like patch 1/1 is not hitting the mailing list.
>>>> How large is it?
>>>
>>> Thank you for catching this:
>>>
>>> [hans@dhcp-44-196 linux]$ wc 0001-fs-Add-VirtualBox-guest-shared-folder-vboxsf-support.patch
>>> 3754 14479 100991 0001-fs-Add-VirtualBox-guest-shared-folder-vboxsf-support.patch
>>
>> That size shouldn't be a problem AFAIK.
>> Maybe there is something else in the patch that vger doesn't like.
>>
>> http://vger.kernel.org/majordomo-taboos.txt
>>
>
> "Message size exceeding 100 000 characters causes blocking."
> from: http://vger.kernel.org/majordomo-info.html
>
> I thought the limit was higher than that.
Thank you for this info. I've trimmed the changelog below the ---
in the commit messages, moving it to the coverletter, this
brings the size down to aprox. 96000 chars and I've done another
resend. Can you please let me know (offlist) if this one has
successfully made it to the list?
Regards,
Hans
next prev parent reply other threads:[~2019-08-11 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 13:38 [PATCH v12 resend 0/1] fs: Add VirtualBox guest shared folder (vboxsf) Hans de Goede
2019-08-11 15:07 ` 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 [this message]
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=4ba48f60-10f7-95dc-d259-68c6e3d4d026@redhat.com \
--to=hdegoede@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdunlap@infradead.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).