lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 1 May 2022 20:58:22 +0300 From: Sergey Shtylyov <s.shtylyov@....ru> To: Rich Felker <dalias@...c.org>, John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de> CC: <linux-sh@...r.kernel.org>, <linux-kernel@...r.kernel.org>, Yoshinori Sato <ysato@...rs.sourceforge.jp>, Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: Re: [PATCH v3] sh: avoid using IRQ0 on SH3/4 On 4/29/22 8:16 PM, Rich Felker wrote: [...] >>> Using IRQ0 by the platform devices is going to be disallowed soon (see [1]) >>> and even now, when IRQ0 is about to be returned by platfrom_get_irq(), you >>> see a big warning. The code supporting SH3/4 SoCs maps the IRQ #s starting >>> at 0 -- modify that code to start the IRQ #s from 16 instead. >>> >>> The patch should mostly affect the AP-SH4A-3A/AP-SH4AD-0A boards as they >>> indeed use IRQ0 for the SMSC911x compatible Ethernet chip... >> >> Maybe try getting it landed through Andrew Morton's tree? > > Hi. I'm alive and looking at it. If it needs to go in for this cycle I > will send a pull request for just this and anything else critical. Was Well, now using IRQ0 just causes a WARNing in platform_get_irq() -- I don't think fixing it is critical enough. Starting from 5.19-rc1 the SMSC91xx driver should stop working on the mentioned boards. But let me look at the SMSC driver itself, I haven't done this yet... > trying to get to it last night but had some unpleasant surprises come > up that took me away from the computer. :-( > Rich MBR, Sergey
Powered by blists - more mailing lists