From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: mtk.manpages@gmail.com, Andrei Vagin <avagin@gmail.com>
Cc: Dmitry Safonov via Containers
<containers@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrey Vagin <avagin@openvz.org>,
Dmitry Safonov <dima@arista.com>,
Linux API <linux-api@vger.kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
stable@kernel.org, Ingo Molnar <mingo@redhat.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Thomas Gleixner <tglx@linutronix.de>,
Adrian Reber <adrian@lisas.de>
Subject: Re: [PATCH] kernel/time: Add max_time_namespaces ucount
Date: Tue, 7 Apr 2020 10:16:25 +0100 [thread overview]
Message-ID: <e6718888-3a18-45da-e091-577c3822d6ac@arm.com> (raw)
In-Reply-To: <CAKgNAkgTdND5m60Adb2O+SnogcUcho15F9cF5sZt_yrDF0REYg@mail.gmail.com>
On 4/7/20 9:22 AM, Michael Kerrisk (man-pages) wrote:
> On Tue, 7 Apr 2020 at 05:31, Andrei Vagin <avagin@gmail.com> wrote:
>>
>> On Mon, Apr 06, 2020 at 06:13:42PM +0100, Dmitry Safonov via Containers wrote:
>>> Introduce missing time namespaces limit per-userns.
>>> Michael noticed that userns limit for number of time namespaces is
>>> missing.
>>>
>>> Furthermore, time namespace introduced UCOUNT_TIME_NAMESPACES, but
>>> didn't introduce an array member in user_table[]. It would make array's
>>> initialisation OOB write, but by luck the user_table array has
>>> an excessive empty member (all accesses to the array are limited with
>>> UCOUNT_COUNTS - so it silently reuses the last free member.
>>>
>>> Fixes user-visible regression: max_inotify_instances by reason of the
>>> missing UCOUNT_ENTRY() has limited max number of namespaces instead of
>>> the number of inotify instances.
>>>
>>> Fixes: 769071ac9f20 ("ns: Introduce Time Namespace")
>>> Cc: Adrian Reber <adrian@lisas.de>
>>> Cc: Andrey Vagin <avagin@openvz.org>
>>> Cc: Christian Brauner <christian.brauner@ubuntu.com>
>>> Cc: Eric W. Biederman <ebiederm@xmission.com>
>>> Cc: Ingo Molnar <mingo@redhat.com>
>>> Cc: Thomas Gleixner <tglx@linutronix.de>
>>> Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
>>> Cc: Containers <containers@lists.linux-foundation.org>
>>> Cc: Linux API <linux-api@vger.kernel.org>
>>> Cc: stable@kernel.org # v5.6+
>>> Reported-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
>>
>> Acked-by: Andrei Vagin <avagin@gmail.com>
>
> Acked-by: Michael Kerrisk <mtk.manpages@gmail.com>
>
>
>
Acked-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2020-04-07 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 17:13 [PATCH] kernel/time: Add max_time_namespaces ucount Dmitry Safonov
2020-04-07 3:31 ` Andrei Vagin
2020-04-07 8:22 ` Michael Kerrisk (man-pages)
2020-04-07 9:16 ` Vincenzo Frascino [this message]
2020-04-07 10:43 ` Christian Brauner
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=e6718888-3a18-45da-e091-577c3822d6ac@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=0x7f454c46@gmail.com \
--cc=adrian@lisas.de \
--cc=avagin@gmail.com \
--cc=avagin@openvz.org \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux-foundation.org \
--cc=dima@arista.com \
--cc=ebiederm@xmission.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).