From: Jan Kara <jack@suse.cz>
To: bingjingc <bingjingc@synology.com>
Cc: viro@zeniv.linux.org.uk, jack@suse.com, jack@suse.cz,
axboe@kernel.dk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, cccheng@synology.com,
robbieko@synology.com, willy@infradead.org,
rdunlap@infradead.org
Subject: Re: [PATCH v2 0/3] handle large user and group ID for isofs and udf
Date: Thu, 28 Jan 2021 11:55:01 +0100 [thread overview]
Message-ID: <20210128105501.GC3324@quack2.suse.cz> (raw)
In-Reply-To: <1611817947-2839-1-git-send-email-bingjingc@synology.com>
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.
2) Please split the cleanup of kernel doc comments in lib/parser.c in a
separate patch. It is unrelated to adding parse_uint() function so it
belongs into a separate patch (we occasionally do include small unrelated
cleanups if they are on the same line we change anyway but your changes
definitely triggered my treshold of this should be a separate patch).
Thanks!
Honza
>
> fs/isofs/inode.c | 9 +++++----
> fs/udf/super.c | 9 +++++----
> include/linux/parser.h | 1 +
> lib/parser.c | 44 +++++++++++++++++++++++++++++++++-----------
> 4 files changed, 44 insertions(+), 19 deletions(-)
>
> --
> 2.7.4
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-01-28 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 7:12 [PATCH v2 0/3] handle large user and group ID for isofs and udf bingjingc
2021-01-28 10:55 ` Jan Kara [this message]
2021-01-28 14:18 ` Matthew Wilcox
[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=20210128105501.GC3324@quack2.suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=bingjingc@synology.com \
--cc=cccheng@synology.com \
--cc=jack@suse.com \
--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 \
--cc=willy@infradead.org \
/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