From: Arnd Bergmann <arnd@arndb.de>
To: Xiong Zhou <jencce.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
nnk@google.com, john.stultz@linaro.org,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: android: logger: fix kuid/uid in logger_entry
Date: Thu, 30 Oct 2014 08:04:44 +0100 [thread overview]
Message-ID: <3175901.1lz7PhpNtK@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.11.1410301007090.3316@dhcp12-144.nay.redhat.com>
On Thursday 30 October 2014 10:23:31 Xiong Zhou wrote:
> From: Xiong Zhou <jencce.kernel@gmail.com>
>
> struct logger_entry can be returned to userspace via ioctl,
> so it is wrong to have a kuid_t member, fixing it to uid_t.
> This was introduced by commit bd471258f2, to pass uidguid
> type checks : UIDGID_STRICT_TYPE_CHECKS, which has been
> removed from kernel in commit 261000a56b6.
>
> Fixes: bd471258f2 (logger: use kuid_t instead of uid_t)
> Signed-off-by: Xiong Zhou <jencce.kernel@gmail.com>
Sorry, but this isn't good.
You had an earlier patch that introduced a bug by hiding a warning,
and now you send a new patch to hide the bug better instead of
fixing it?
> diff --git a/drivers/staging/android/logger.c b/drivers/staging/android/logger.c
> index 28b93d3..fb06bf2 100644
> --- a/drivers/staging/android/logger.c
> +++ b/drivers/staging/android/logger.c
> @@ -252,7 +252,7 @@ static size_t get_next_entry_by_uid(struct logger_log *log,
>
> entry = get_entry_header(log, off, &scratch);
>
> - if (uid_eq(entry->euid, euid))
> + if (entry->euid == __kuid_val(euid))
> return off;
>
> next_len = sizeof(struct logger_entry) + entry->len;
The code above was correct, you are just breaking it more.
> @@ -430,7 +430,7 @@ static ssize_t logger_write_iter(struct kiocb *iocb, struct iov_iter *from)
> header.tid = current->pid;
> header.sec = now.tv_sec;
> header.nsec = now.tv_nsec;
> - header.euid = current_euid();
> + header.euid = __kuid_val(current_euid());
> header.len = count;
> header.hdr_size = sizeof(struct logger_entry);
>
This writes to the internal data structure, so here you should still use
kuid_t. The problem is that you are later leaking this to user space,
so a user in one container can read entries from a user with the same
uid in another container, and that a process calling read() with the
r_all bit set will get entries with uids from all containers, using
the kernel-internal uid values instead of the ones valid for the current
container.
Arnd
prev parent reply other threads:[~2014-10-30 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 2:23 Xiong Zhou
2014-10-30 7:04 ` Arnd Bergmann [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=3175901.1lz7PhpNtK@wuerfel \
--to=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jencce.kernel@gmail.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nnk@google.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 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®