stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
	"kernelci.org bot" <bot@kernelci.org>,
	Kernel Build Reports Mailman List
	<kernel-build-reports@lists.linaro.org>,
	Hugh Dickins <hughd@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	"4.4.x" <stable@vger.kernel.org>
Subject: Re: stable-rc/linux-4.4.y build: 178 builds: 7 failed, 171 passed, 8 errors (v4.4.110-23-g49278737d445)
Date: Mon, 8 Jan 2018 18:36:50 +0100	[thread overview]
Message-ID: <20180108173650.b6ip2yaycr47feib@gmail.com> (raw)
In-Reply-To: <20180108160646.tqdgojirykmhsezn@pd.tnic>


* Borislav Petkov <bp@suse.de> wrote:

> On Mon, Jan 08, 2018 at 03:43:11PM +0100, Arnd Bergmann wrote:
> > This comes from 0cbf2b590bea ("Map the vsyscall page with _PAGE_USER")
> > which adds a line 'bool vsyscall_enabled(void) { return false; }' that
> > presumably
> > should have been 'static inline'.
> 
> Yeah, thanks Arnd.
> 
> @Greg, please fold this in:
> 
> ---
> diff --git a/arch/x86/include/asm/vsyscall.h b/arch/x86/include/asm/vsyscall.h
> index d10cabb..4865e10 100644
> --- a/arch/x86/include/asm/vsyscall.h
> +++ b/arch/x86/include/asm/vsyscall.h
> @@ -19,7 +19,7 @@ static inline bool emulate_vsyscall(struct pt_regs *regs, unsigned long address)
>  {
>  	return false;
>  }
> -bool vsyscall_enabled(void) { return false; }
> +static inline bool vsyscall_enabled(void) { return false; }

Hm, which are the underlying upstream commits - am I missing something?

Thanks,

	Ingo

  parent reply	other threads:[~2018-01-08 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5a537ac1.b0abdf0a.c8456.4e12@mx.google.com>
2018-01-08 14:43 ` stable-rc/linux-4.4.y build: 178 builds: 7 failed, 171 passed, 8 errors (v4.4.110-23-g49278737d445) Arnd Bergmann
2018-01-08 16:06   ` Borislav Petkov
2018-01-08 16:29     ` Greg Kroah-Hartman
2018-01-08 17:36     ` Ingo Molnar [this message]
2018-01-08 17:41       ` Borislav Petkov

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=20180108173650.b6ip2yaycr47feib@gmail.com \
    --to=mingo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bot@kernelci.org \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).