All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
	Alexey Gladkov <legion@kernel.org>,
	Rune Kleveland <rune.kleveland@infomedia.dk>,
	Yu Zhao <yuzhao@google.com>,
	Jordan Glover <Golden_Miller83@protonmail.ch>,
	Antoine Martin <antoine@nagafix.co.uk>,
	David Howells <dhowells@redhat.com>,
	Jarkko Sakkinen <jarkko@kernel.org>
Subject: [GIT PULL] ucount cleanups for v5.16
Date: Tue, 02 Nov 2021 14:01:00 -0500	[thread overview]
Message-ID: <87bl325qmr.fsf@disp2133> (raw)


Linus,

Please pull the ucount-fixes-for-v5.16 branch from the git tree:

  git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git ucount-fixes-for-v5.16

  HEAD: 32342701b4ba57a6fd77e8aca2f65f68c0fa1da6 ucounts: Use atomic_long_sub_return for clarity

While working on the ucount fixes a for v5.15 a number of cleanups
suggested themselves.  Little things like not testing for NULL when a
pointer can not be NULL and wrapping atomic_add_negative with a more
descriptive name, so that people reading the code can more quickly
understand what is going on.

Eric W. Biederman (4):
      ucounts: In set_cred_ucounts assume new->ucounts is non-NULL
      ucounts: Remove unnecessary test for NULL ucount in get_ucounts
      ucounts: Add get_ucounts_or_wrap for clarity
      ucounts: Use atomic_long_sub_return for clarity

 kernel/cred.c   |  5 ++---
 kernel/ucount.c | 20 +++++++++++++-------
 2 files changed, 15 insertions(+), 10 deletions(-)

Eric

             reply	other threads:[~2021-11-02 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 19:01 Eric W. Biederman [this message]
2021-11-02 22:57 ` [GIT PULL] ucount cleanups for v5.16 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=87bl325qmr.fsf@disp2133 \
    --to=ebiederm@xmission.com \
    --cc=Golden_Miller83@protonmail.ch \
    --cc=antoine@nagafix.co.uk \
    --cc=dhowells@redhat.com \
    --cc=jarkko@kernel.org \
    --cc=legion@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rune.kleveland@infomedia.dk \
    --cc=torvalds@linux-foundation.org \
    --cc=yuzhao@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 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.