From: Christian Brauner <christian.brauner@ubuntu.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] misc fixes for v5.11-rc5
Date: Sun, 24 Jan 2021 13:51:22 +0100 [thread overview]
Message-ID: <20210124125121.3969248-1-christian.brauner@ubuntu.com> (raw)
Hi Linus,
Here are some fixes for v5.11-rc5 that should hopefully be fairly
uncontroversial. I've had them sitting around for a bit but only got around
sending them now after concluding the idmapped mounts stuff. Sorry for the
delay.
/* Summary */
- Jann reported sparse complaints because of a missing __user annotation in a
helper we added way back when we added pidfd_send_signal() to avoid compat
syscall handling. This contains a fix for this.
- Yanfei replaces a reference in a comment to the _do_fork() helper I removed a
while ago with a reference to the new kernel_clone() replacement.
- Alexander Guril added a simple coding style fix.
The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837:
Linux 5.11-rc3 (2021-01-10 14:34:50 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/for-linus-2021-01-24
for you to fetch changes up to cb5021ca622fe83923e0789f99fe7227cbcd3f68:
kthread: remove comments about old _do_fork() helper (2021-01-11 15:11:56 +0100)
/* Testing */
The patches have been sitting in -next for a while. No build failures or
warnings were observed. All old and new tests are passing.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflict with e1ae4b0be158 ("Merge branch 'mtd/fixes'
of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux") when pulling the
tag.
Please consider pulling these changes from the signed for-linus-2021-01-24 tag.
Thanks!
Christian
----------------------------------------------------------------
for-linus-2021-01-24
----------------------------------------------------------------
Alexander Guril (1):
Kernel: fork.c: Fix coding style: Do not use {} around single-line statements
Jann Horn (1):
signal: Add missing __user annotation to copy_siginfo_from_user_any
Yanfei Xu (1):
kthread: remove comments about old _do_fork() helper
include/trace/events/sched.h | 2 +-
kernel/fork.c | 6 ++----
kernel/kthread.c | 2 +-
kernel/signal.c | 3 ++-
4 files changed, 6 insertions(+), 7 deletions(-)
next reply other threads:[~2021-01-24 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 12:51 Christian Brauner [this message]
2021-01-24 18:34 ` 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=20210124125121.3969248-1-christian.brauner@ubuntu.com \
--to=christian.brauner@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®