From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alexey Gladkov <legion@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.linux.dev>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v2] Fix UCOUNT_RLIMIT_SIGPENDING counter leak
Date: Thu, 8 Jul 2021 11:44:05 -0700 [thread overview]
Message-ID: <CAHk-=whdEAjawjUSeJ+DV25ARdAhbiW_HZM65ZgJx7M94rvLkg@mail.gmail.com> (raw)
In-Reply-To: <20210708103301.2109330-1-legion@kernel.org>
On Thu, Jul 8, 2021 at 3:34 AM Alexey Gladkov <legion@kernel.org> wrote:
>
> We must properly handle an errors when we increase the rlimit counter
> and the ucounts reference counter. We have to this with RCU protection
> to prevent possible use-after-free that could occur due to concurrent
> put_cred_rcu().
Thanks, LGTM. Applied,
Linus
next prev parent reply other threads:[~2021-07-08 18:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 22:35 [GIT PULL] ucounts: Count rlimits in each user namespace Eric W. Biederman
2021-06-29 3:47 ` Linus Torvalds
2021-06-29 15:04 ` Eric W. Biederman
2021-06-29 15:51 ` Eric W. Biederman
2021-06-29 16:34 ` Linus Torvalds
2021-06-29 16:42 ` Eric W. Biederman
2021-06-29 17:09 ` Eric W. Biederman
2021-07-01 16:41 ` Alexey Gladkov
2021-07-01 20:05 ` Eric W. Biederman
2021-06-29 17:17 ` Alexey Gladkov
2021-06-29 18:07 ` Linus Torvalds
2021-06-29 20:20 ` Alexey Gladkov
2021-06-29 20:33 ` Linus Torvalds
2021-06-29 21:22 ` Alexey Gladkov
2021-07-02 17:54 ` [PATCH] ucounts: Fix UCOUNT_RLIMIT_SIGPENDING counter leak Alexey Gladkov
2021-07-02 22:13 ` Linus Torvalds
2021-07-07 16:50 ` Alexey Gladkov
2021-07-07 17:23 ` Linus Torvalds
2021-07-08 10:33 ` [PATCH v2] " Alexey Gladkov
2021-07-08 18:44 ` Linus Torvalds [this message]
2021-07-08 11:00 ` [PATCH] ucounts: " Alexey Gladkov
2021-06-29 3:50 ` [GIT PULL] ucounts: Count rlimits in each user namespace pr-tracker-bot
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='CAHk-=whdEAjawjUSeJ+DV25ARdAhbiW_HZM65ZgJx7M94rvLkg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=containers@lists.linux.dev \
--cc=ebiederm@xmission.com \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.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;
as well as URLs for NNTP newsgroup(s).