From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Aditya Garg <gargaditya08@live.com>
Cc: "willy@infradead.org" <willy@infradead.org>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"songmuchun@bytedance.com" <songmuchun@bytedance.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] hfsplus: Fix bug causing custom uid and gid being unable to be assigned with mount
Date: Wed, 7 Dec 2022 12:17:14 -0800 [thread overview]
Message-ID: <082FE5D4-5B72-4B4F-AC00-E0D52C7F8758@dubeyko.com> (raw)
In-Reply-To: <C0264BF5-059C-45CF-B8DA-3A3BD2C803A2@live.com>
> On Dec 6, 2022, at 7:05 PM, Aditya Garg <gargaditya08@live.com> wrote:
>
> From: Aditya Garg <gargaditya08@live.com>
>
> Despite specifying UID and GID in mount command, the specified UID and GID
> were not being assigned. This patch fixes this issue.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Aditya Garg <gargaditya08@live.com>
> ---
> fs/hfsplus/hfsplus_fs.h | 2 ++
> fs/hfsplus/inode.c | 4 ++--
> fs/hfsplus/options.c | 4 ++++
> 3 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/fs/hfsplus/hfsplus_fs.h b/fs/hfsplus/hfsplus_fs.h
> index a5db2e3b2..6aa919e59 100644
> --- a/fs/hfsplus/hfsplus_fs.h
> +++ b/fs/hfsplus/hfsplus_fs.h
> @@ -198,6 +198,8 @@ struct hfsplus_sb_info {
> #define HFSPLUS_SB_HFSX 3
> #define HFSPLUS_SB_CASEFOLD 4
> #define HFSPLUS_SB_NOBARRIER 5
> +#define HFSPLUS_SB_UID 6
> +#define HFSPLUS_SB_GID 7
>
> static inline struct hfsplus_sb_info *HFSPLUS_SB(struct super_block *sb)
> {
> diff --git a/fs/hfsplus/inode.c b/fs/hfsplus/inode.c
> index aeab83ed1..b675581aa 100644
> --- a/fs/hfsplus/inode.c
> +++ b/fs/hfsplus/inode.c
> @@ -192,11 +192,11 @@ static void hfsplus_get_perms(struct inode *inode,
> mode = be16_to_cpu(perms->mode);
>
> i_uid_write(inode, be32_to_cpu(perms->owner));
> - if (!i_uid_read(inode) && !mode)
> + if ((test_bit(HFSPLUS_SB_UID, &sbi->flags)) || (!i_uid_read(inode) && !mode))
> inode->i_uid = sbi->uid;
>
> i_gid_write(inode, be32_to_cpu(perms->group));
> - if (!i_gid_read(inode) && !mode)
> + if ((test_bit(HFSPLUS_SB_GID, &sbi->flags)) || (!i_gid_read(inode) && !mode))
> inode->i_gid = sbi->gid;
>
> if (dir) {
> diff --git a/fs/hfsplus/options.c b/fs/hfsplus/options.c
> index 047e05c57..c94a58762 100644
> --- a/fs/hfsplus/options.c
> +++ b/fs/hfsplus/options.c
> @@ -140,6 +140,8 @@ int hfsplus_parse_options(char *input, struct hfsplus_sb_info *sbi)
> if (!uid_valid(sbi->uid)) {
> pr_err("invalid uid specified\n");
> return 0;
> + } else {
> + set_bit(HFSPLUS_SB_UID, &sbi->flags);
> }
> break;
> case opt_gid:
> @@ -151,6 +153,8 @@ int hfsplus_parse_options(char *input, struct hfsplus_sb_info *sbi)
> if (!gid_valid(sbi->gid)) {
> pr_err("invalid gid specified\n");
> return 0;
> + } else {
> + set_bit(HFSPLUS_SB_GID, &sbi->flags);
> }
> break;
> case opt_part:
> --
> 2.38.1
>
Looks good.
Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>
Thanks,
Slava.
prev parent reply other threads:[~2022-12-07 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 15:39 [PATCH] " Aditya Garg
2022-12-02 20:52 ` Viacheslav Dubeyko
2022-12-03 7:56 ` Aditya Garg
2022-12-06 0:35 ` Viacheslav Dubeyko
2022-12-06 8:12 ` Aditya Garg
2022-12-06 8:49 ` Aditya Garg
2022-12-06 18:56 ` Viacheslav Dubeyko
2022-12-07 3:04 ` Aditya Garg
2022-12-07 3:05 ` [PATCH v2] " Aditya Garg
2022-12-07 20:17 ` Viacheslav Dubeyko [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=082FE5D4-5B72-4B4F-AC00-E0D52C7F8758@dubeyko.com \
--to=slava@dubeyko.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gargaditya08@live.com \
--cc=ira.weiny@intel.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®