From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: linux-tip-commits@vger.kernel.org
Cc: Vladis Dronov <vdronov@redhat.com>
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [tip: efi/urgent] efi: Add a sanity check to efivar_store_raw()
Date: Mon, 09 Mar 2020 12:25:03 +0000 [thread overview]
Message-ID: <20200309122504.3DA3A20848@mail.kernel.org> (raw)
In-Reply-To: <158368551265.28353.5476421599260286182.tip-bot2@tip-bot2>
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.5.8, v5.4.24, v4.19.108, v4.14.172, v4.9.215, v4.4.215.
v5.5.8: Build OK!
v5.4.24: Build OK!
v4.19.108: Failed to apply! Possible dependencies:
98f76206b335 ("compat: Cleanup in_compat_syscall() callers")
v4.14.172: Failed to apply! Possible dependencies:
98f76206b335 ("compat: Cleanup in_compat_syscall() callers")
ea2ce8f3514e ("time: Fix get_timespec64() for y2038 safe compat interfaces")
v4.9.215: Failed to apply! Possible dependencies:
31ea70e0308b ("posix-timers: Move the do_schedule_next_timer declaration")
96fe3b072f13 ("posix-timers: Rename do_schedule_next_timer")
98f76206b335 ("compat: Cleanup in_compat_syscall() callers")
d5b7ffbfbdac ("time: introduce {get,put}_itimerspec64")
ea2ce8f3514e ("time: Fix get_timespec64() for y2038 safe compat interfaces")
f59dd9c886ac ("time: add get_timespec64 and put_timespec64")
v4.4.215: Failed to apply! Possible dependencies:
2bf8c4762659 ("net/xfrm_user: use in_compat_syscall to deny compat syscalls")
31ea70e0308b ("posix-timers: Move the do_schedule_next_timer declaration")
4f01ed221e2e ("drivers/firmware/efi/efivars.c: use in_compat_syscall() to check for compat callers")
96fe3b072f13 ("posix-timers: Rename do_schedule_next_timer")
98f76206b335 ("compat: Cleanup in_compat_syscall() callers")
bc2c53e5f1a2 ("time: add missing implementation for timespec64_add_safe()")
d5b7ffbfbdac ("time: introduce {get,put}_itimerspec64")
ea2ce8f3514e ("time: Fix get_timespec64() for y2038 safe compat interfaces")
f59dd9c886ac ("time: add get_timespec64 and put_timespec64")
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-03-09 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200305084041.24053-3-vdronov@redhat.com>
2020-03-08 16:38 ` [tip: efi/urgent] efi: Add a sanity check to efivar_store_raw() tip-bot2 for Vladis Dronov
2020-03-09 12:25 ` Sasha Levin [this message]
2020-03-09 12:38 ` Vladis Dronov
2020-03-16 14:21 ` Vladis Dronov
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=20200309122504.3DA3A20848@mail.kernel.org \
--to=sashal@kernel.org \
--cc=vdronov@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