From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
To: 1vier1@web.de, akpm@linux-foundation.org, dave@stgolabs.net
Cc: Davidlohr Bueso <dave@stgolabs.net>
Cc: Markus Elfring <elfring@users.sourceforge.net>
Cc: <1vier1@web.de>
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [patch 01/15] ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()
Date: Sat, 09 May 2020 12:30:52 +0000 [thread overview]
Message-ID: <20200509123053.8336121775@mail.kernel.org> (raw)
In-Reply-To: <20200508013539.Q-iufOGqB%akpm@linux-foundation.org>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: cc731525f26a ("signal: Remove kernel interal si_code magic").
The bot has tested the following trees: v5.6.11, v5.4.39, v4.19.121, v4.14.179.
v5.6.11: Build OK!
v5.4.39: Build OK!
v4.19.121: Failed to apply! Possible dependencies:
4cd2e0e70af6 ("signal: Introduce copy_siginfo_from_user and use it's return value")
ae7795bc6187 ("signal: Distinguish between kernel_siginfo and siginfo")
efc463adbccf ("signal: Simplify tracehook_report_syscall_exit")
v4.14.179: Failed to apply! Possible dependencies:
212a36a17efe ("signal: Unify and correct copy_siginfo_from_user32")
3eb0f5193b49 ("signal: Ensure every siginfo we send has all bits initialized")
3f7c86b2382e ("arm64: Update fault_info table with new exception types")
526c3ddb6aa2 ("signal/arm64: Document conflicts with SI_USER and SIGFPE,SIGTRAP,SIGBUS")
532826f3712b ("arm64: Mirror arm for unimplemented compat syscalls")
6b4f3d01052a ("usb, signal, security: only pass the cred, not the secid, to kill_pid_info_as_cred and security_task_kill")
92ff0674f5d8 ("arm64: mm: Rework unhandled user pagefaults to call arm64_force_sig_info")
ae7795bc6187 ("signal: Distinguish between kernel_siginfo and siginfo")
af40ff687bc9 ("arm64: signal: Ensure si_code is valid for all fault signals")
b713da69e4c9 ("signal: unify compat_siginfo_t")
ea64d5acc8f0 ("signal: Unify and correct copy_siginfo_to_user32")
efc463adbccf ("signal: Simplify tracehook_report_syscall_exit")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-05-09 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200507183509.c5ef146c5aaeb118a25a39a8@linux-foundation.org>
2020-05-08 1:35 ` [patch 01/15] ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() Andrew Morton
2020-05-09 12:30 ` Sasha Levin [this message]
2020-05-08 1:35 ` [patch 03/15] mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous() Andrew Morton
2020-05-08 1:35 ` [patch 07/15] eventpoll: fix missing wakeup for ovflist in ep_poll_callback Andrew Morton
2020-05-08 1:36 ` [patch 12/15] epoll: atomically remove wait entry on wake up Andrew Morton
2020-05-08 1:36 ` [patch 15/15] mm: limit boost_watermark on small zones Andrew Morton
2020-05-08 23:53 ` + device-dax-dont-leak-kernel-memory-to-user-space-after-unloading-kmem.patch added to -mm tree Andrew Morton
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=20200509123053.8336121775@mail.kernel.org \
--to=sashal@kernel.org \
--cc=dave@stgolabs.net \
/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).