From: ebiederm@xmission.com (Eric W. Biederman)
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: [PATCH 1/2] fs: add inode helpers for fsuid and fsgid
Date: Tue, 14 Feb 2017 20:46:32 +1300 [thread overview]
Message-ID: <87lgt9mcyv.fsf@xmission.com> (raw)
In-Reply-To: <1487053720.3125.73.camel@HansenPartnership.com> (James Bottomley's message of "Mon, 13 Feb 2017 22:28:40 -0800")
James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> Now that we have two different views of filesystem ids (the filesystem
> view and the kernel view), we have a problem in that
> current_fsuid/fsgid() return the kernel view but are sometimes used in
> filesystem code where the filesystem view shoud be used. This patch
> introduces helpers to produce the filesystem view of current fsuid and
> fsgid.
If I am reading this right what we are seeing is that xfs explicitly
opted out of type safety with predictable results. Accidentally
confusing kuids and uids, which is potentially security issue.
All of that said where are you getting sb->s_user_ns != &init_user_ns
for an xfs filesystem? There are quite a few xfs interfaces that are
not ready for that. xfs has a very wide userspace interface of ioctls
that all needs to be looked at and addressed carefully if there is
anything like this going on.
I think we really need to ask if we should use kuids and kgids for the
xfs internal quota code. At the end of the day that is going to be
a whole lot less error prone.
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
>
> diff --git a/include/linux/cred.h b/include/linux/cred.h
> index f0e70a1..18e9c41 100644
> --- a/include/linux/cred.h
> +++ b/include/linux/cred.h
> @@ -399,4 +399,9 @@ do { \
> *(_fsgid) = __cred->fsgid; \
> } while(0)
>
> +/* return the current id in the filesystem view */
> +#define i_fsuid(i) from_kuid((i)->i_sb->s_user_ns, current_fsuid())
> +#define i_fsgid(i) from_kgid((i)->i_sb->s_user_ns, current_fsgid())
Could we please place these helpers in fs.h?
That should allow them to become inline functions and live with the
existing filesystem helpers in there.
My gut says the names disk_fsuid(i) and disk_fsgid(i) would be clearer.
Of course all of this has the challenge of error handling in the case
when current_fsuid or current_fsgid do not map into the current
filesystem.
Eric
next prev parent reply other threads:[~2017-02-14 7:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 17:46 xfs: fix inode uid/gid initialization James Bottomley
2017-02-13 19:43 ` Christoph Hellwig
2017-02-13 20:33 ` James Bottomley
2017-02-13 21:34 ` Dave Chinner
2017-02-14 6:08 ` Christoph Hellwig
2017-02-14 6:27 ` James Bottomley
2017-02-14 6:28 ` [PATCH 1/2] fs: add inode helpers for fsuid and fsgid James Bottomley
2017-02-14 7:46 ` Eric W. Biederman [this message]
2017-02-14 8:00 ` Christoph Hellwig
2017-02-14 16:09 ` James Bottomley
2017-02-15 2:29 ` Eric W. Biederman
2017-02-16 15:43 ` James Bottomley
2017-02-17 1:15 ` Eric W. Biederman
2017-02-17 17:12 ` James Bottomley
2017-02-20 4:56 ` Eric W. Biederman
2017-02-14 6:29 ` [PATCH 2/2] xfs: fix inode uid/gid initialization James Bottomley
2017-02-14 7:58 ` Christoph Hellwig
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=87lgt9mcyv.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=seth.forshee@canonical.com \
/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.