[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvxcz78aKRAHOz=oLCNFk-Xxm4sFMJk9DiR6aZOEbZ0Nog@mail.gmail.com>
Date: Wed, 7 Oct 2020 15:01:05 +0200
From: Richard Weinberger <richard.weinberger@...il.com>
To: Paul Bolle <pebolle@...cali.nl>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Richard Weinberger <richard@....at>,
Anton Ivanov <anton.ivanov@...bridgegreys.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Linus Walleij <linus.walleij@...aro.org>,
Nick Hu <nickhu@...estech.com>,
Greentime Hu <green.hu@...il.com>,
Vincent Chen <deanbo422@...il.com>
Subject: Re: Build regressions/improvements in v5.9-rc8
On Wed, Oct 7, 2020 at 2:47 PM Paul Bolle <pebolle@...cali.nl> wrote:
>
> Richard Weinberger schreef op wo 07-10-2020 om 14:08 [+0200]:
> > UML has no ia32 emulation and therefore no in_ia32_syscall().
> > Maybe you can check for CONFIG_IA32_EMULATION too?
>
> The pending fix is:
> #if defined(CONFIG_X86_64) && !defined(CONFIG_UML)
>
> Since this check guards in_ia32_syscall() just checking CONFIG_IA32_EMULATION
> should do too.
>
> (Way outside my limited expertise, but anyway: is does look odd to see a call
> to in_ia32_syscall() in drivers/. All other calls are in arch/x86/. Isn't this
> a bit too x86 specific for an arch independent driver?)
Indeed. in_compat_syscall() seems to be more suitable.
But for UML this does not really help, I fear, it has also no CONFIG_COMPAT.
--
Thanks,
//richard
Powered by blists - more mailing lists