[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <daf484e9-7f3d-9c76-d4c4-a054dcf236c1@arista.com>
Date: Wed, 1 Apr 2020 15:41:29 +0100
From: Dmitry Safonov <dima@...sta.com>
To: Michael Ellerman <mpe@...erman.id.au>, linux-kernel@...r.kernel.org
Cc: Dmitry Safonov <0x7f454c46@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Iurii Zaikin <yzaikin@...gle.com>,
Jiri Slaby <jslaby@...e.com>, Joe Perches <joe@...ches.com>,
Randy Dunlap <rdunlap@...radead.org>,
Vasiliy Khoruzhick <vasilykh@...sta.com>,
linux-serial@...r.kernel.org, Luis Chamberlain <mcgrof@...nel.org>,
Kees Cook <keescook@...omium.org>,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCHv3 1/2] sysctl/sysrq: Remove __sysrq_enabled copy
Hi Michael,
On 4/1/20 1:22 PM, Michael Ellerman wrote:
[..]
>>
>> +/**
>> + * sysrq_mask - Getter for sysrq_enabled mask.
>> + *
>> + * Return: 1 if sysrq is always enabled, enabled sysrq_key_op mask otherwise.
>> + */
>> +int sysrq_mask(void)
>> +{
>> + if (sysrq_always_enabled)
>> + return 1;
>> + return sysrq_enabled;
>> +}
>
> This seems to have broken several configs, when serial_core is modular, with:
>
> ERROR: modpost: "sysrq_mask" [drivers/tty/serial/serial_core.ko] undefined!
>
> See:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/14169386/
>
> It's also being reported by the kernelci bot:
>
> https://lore.kernel.org/linux-next/5e677bd0.1c69fb81.c43fe.7f7d@mx.google.com/
Thanks for reporting this,
I've reproduced it and sent a fix:
https://lkml.kernel.org/r/20200401143904.423450-1-dima@arista.com
Thanks,
Dmitry
Powered by blists - more mailing lists