From: Borislav Petkov <bp@alien8.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Jethro Beekman <jethro@fortanix.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH] x86/vdso: Use proper modifier for len's printf in extract
Date: Thu, 4 Mar 2021 12:04:41 +0100 [thread overview]
Message-ID: <20210304110441.GD15496@zn.tnic> (raw)
In-Reply-To: <f397fa13-5cec-ca09-7c5e-9e99c223bb24@suse.cz>
On Thu, Mar 04, 2021 at 11:55:18AM +0100, Jiri Slaby wrote:
> On 04. 03. 21, 11:48, Borislav Petkov wrote:
> > On Thu, Mar 04, 2021 at 06:18:25AM +0100, Jiri Slaby wrote:
> > > It's built with gcc 10 from tumbleweed and it's a standard config from
> > > kerncvs:
> > > https://github.com/openSUSE/kernel-source/blob/stable/config/i386/pae
> >
> > Nope, can't trigger with that one either. :-\
>
> Beware:
> HOSTCC arch/x86/entry/vdso/vdso2c
> ^^^^^^
> You would need to _be_ on i586. Or try with -m32:
Yah, that is the explanation. I would've never seen because - although I
do the regular 32-bit builds - I don't do them on a 32-bit platform. But
hey, OBS does. :)
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-03-04 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 6:43 [PATCH] x86/vdso: Use proper modifier for len's printf in extract Jiri Slaby
2021-03-03 15:28 ` Jarkko Sakkinen
2021-03-03 18:36 ` Borislav Petkov
2021-03-04 5:18 ` Jiri Slaby
2021-03-04 10:48 ` Borislav Petkov
2021-03-04 10:55 ` Jiri Slaby
2021-03-04 11:04 ` Borislav Petkov [this message]
2021-03-04 10:54 ` [tip: x86/vdso] x86/vdso: Use proper modifier for len's format specifier in extract() tip-bot2 for Jiri Slaby
2021-03-06 10:38 ` tip-bot2 for Jiri Slaby
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=20210304110441.GD15496@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=jethro@fortanix.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--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