From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH 4.4 1/2] x86/vdso: Remove direct HPET mapping into userspace
Date: Sun, 27 Oct 2019 14:50:13 +0100 [thread overview]
Message-ID: <20191027135013.GA2232759@kroah.com> (raw)
In-Reply-To: <00665546-4ad7-758c-d205-02f2fdca7e6e@yandex-team.ru>
On Wed, Oct 23, 2019 at 04:05:47PM +0300, Konstantin Khlebnikov wrote:
> On 23/10/2019 15.07, Konstantin Khlebnikov wrote:
> > commit 1ed95e52d902035e39a715ff3a314a893a96e5b7 upstream.
> >
> > Commit d96d87834d5b870402a4a5b565706a4869ebc020 in v4.4.190 which is
> > backport of upstream commit 1ed95e52d902035e39a715ff3a314a893a96e5b7
> > removed only HPET access from vdso but leaved HPET mapped in "vvar".
> > So userspace still could read HPET directly and confuse hardware.
> >
> > This patch removes mapping HPET page into userspace.
> >
> > Fixes: d96d87834d5b ("x86/vdso: Remove direct HPET access through the vDSO") # v4.4.190
> > Signed-off-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
> > Link: https://lore.kernel.org/lkml/6fd42b2b-e29a-1fd6-03d1-e9da9192e6c5@yandex-team.ru/
> > ---
> > arch/x86/entry/vdso/vma.c | 14 --------------
> > 1 file changed, 14 deletions(-)
> >
> > diff --git a/arch/x86/entry/vdso/vma.c b/arch/x86/entry/vdso/vma.c
> > index 6b46648588d8..cc0a3c16a95d 100644
> > --- a/arch/x86/entry/vdso/vma.c
> > +++ b/arch/x86/entry/vdso/vma.c
> > @@ -18,7 +18,6 @@
> > #include <asm/vdso.h>
> > #include <asm/vvar.h>
> > #include <asm/page.h>
> > -#include <asm/hpet.h>
> > #include <asm/desc.h>
> > #include <asm/cpufeature.h>
> > @@ -159,19 +158,6 @@ static int map_vdso(const struct vdso_image *image, bool calculate_addr)
> > if (ret)
> > goto up_fail;
> > -#ifdef CONFIG_HPET_TIMER
> > - if (hpet_address && image->sym_hpet_page) {
>
> Probably this patch is not required.
> It seems after removing symbol "hpet_page" from vdso code
> image->sym_hpet_page always is NULL and this branch never executed.
Ok, so these two patches are not needed? I'll drop them from my
todo-queue, thanks.
greg k-h
prev parent reply other threads:[~2019-10-27 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 12:07 [PATCH 4.4 1/2] x86/vdso: Remove direct HPET mapping into userspace Konstantin Khlebnikov
2019-10-23 12:07 ` [PATCH 4.4 2/2] x86/vdso: Remove hpet_page from vDSO Konstantin Khlebnikov
2019-10-23 13:05 ` [PATCH 4.4 1/2] x86/vdso: Remove direct HPET mapping into userspace Konstantin Khlebnikov
2019-10-27 13:50 ` Greg Kroah-Hartman [this message]
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=20191027135013.GA2232759@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).