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: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 8:55 [PATCH] efi: fix a race and a buffer overflow while reading efivars via sysfs Vladis Dronov
2020-03-03 9:15 ` Ard Biesheuvel
2020-03-03 10:14 ` Vladis Dronov
2020-03-03 10:20 ` Ard Biesheuvel
2020-03-03 10:24 ` Vladis Dronov
2020-03-04 6:51 ` joeyli
2020-03-04 15:45 ` Vladis Dronov
2020-03-04 15:47 ` Ard Biesheuvel
2020-03-04 15:49 ` [PATCH v2] " Vladis Dronov
2020-03-04 15:57 ` Ard Biesheuvel
2020-03-04 17:18 ` Vladis Dronov
2020-03-04 17:21 ` Ard Biesheuvel
2020-03-05 6:01 ` joeyli
2020-03-05 6:17 ` Vladis Dronov
2020-03-05 8:40 ` [PATCH v3 0/3] efi: fix a race and add a sanity check Vladis Dronov
2020-03-05 8:40 ` [PATCH v3 1/3] efi: fix a race and a buffer overflow while reading efivars via sysfs Vladis Dronov
2020-03-05 8:45 ` Ard Biesheuvel
2020-03-05 10:52 ` Vladis Dronov
2020-03-08 16:38 ` [tip: efi/urgent] efi: Fix " tip-bot2 for Vladis Dronov
2020-03-05 8:40 ` [PATCH v3 2/3] efi: add a sanity check to efivar_store_raw() Vladis Dronov
2020-03-08 16:38 ` [tip: efi/urgent] efi: Add " 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
2020-03-05 8:40 ` [PATCH v3 3/3] efi: fix a mistype in comments mentioning efivar_entry_iter_begin() Vladis Dronov
2020-03-05 8:51 ` [PATCH v3 0/3] efi: fix a race and add a sanity check Ard Biesheuvel
2020-03-04 14:07 ` [PATCH] efi: fix a race and a buffer overflow while reading efivars via sysfs joeyli
2020-03-04 16:06 ` 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 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.