From: Matthew Wilcox <willy@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: bingjingc <bingjingc@synology.com>,
viro@zeniv.linux.org.uk, jack@suse.com, axboe@kernel.dk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
cccheng@synology.com, robbieko@synology.com,
rdunlap@infradead.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v2 0/3] handle large user and group ID for isofs and udf
Date: Thu, 28 Jan 2021 14:18:56 +0000 [thread overview]
Message-ID: <20210128141856.GX308988@casper.infradead.org> (raw)
In-Reply-To: <20210128105501.GC3324@quack2.suse.cz>
On Thu, Jan 28, 2021 at 11:55:01AM +0100, Jan Kara wrote:
> On Thu 28-01-21 15:12:27, bingjingc wrote:
> > From: BingJing Chang <bingjingc@synology.com>
> >
> > The uid/gid (unsigned int) of a domain user may be larger than INT_MAX.
> > The parse_options of isofs and udf will return 0, and mount will fail
> > with -EINVAL. These patches try to handle large user and group ID.
> >
> > BingJing Chang (3):
> > parser: add unsigned int parser
> > isofs: handle large user and group ID
> > udf: handle large user and group ID
>
> Thanks for your patches! Just two notes:
>
> 1) I don't think Matthew Wilcox gave you his Reviewed-by tag (at least I
> didn't see such email). Generally the rule is that the developer has to
> explicitely write in his email that you can attach his Reviewed-by tag for
> it to be valid.
Right, I didn't.
Looking at fuse, they deleted their copy of match_uint
in favour of switching to the fs_parameter_spec (commit
c30da2e981a703c6b1d49911511f7ade8dac20be) and I wonder if isofs & udf
shouldn't receive the same attention.
next prev parent reply other threads:[~2021-01-28 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 7:12 bingjingc
2021-01-28 10:55 ` Jan Kara
2021-01-28 14:18 ` Matthew Wilcox [this message]
[not found] ` <82e0e4d1-efd0-46d9-aee2-61288efcc3ed@Mail>
2021-01-29 5:33 ` bingjing chang
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=20210128141856.GX308988@casper.infradead.org \
--to=willy@infradead.org \
--cc=axboe@kernel.dk \
--cc=bingjingc@synology.com \
--cc=cccheng@synology.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robbieko@synology.com \
--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®