linux-kernel - Re: [PATCH] m68k: mvme147: Fix SCSI controller IRQ numbers

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFr9PXn8Wi8btubVXKTNNQQyQRtvWaYV5aHyvvQLypJYp5i=9A@mail.gmail.com>
Date: Sat, 2 Nov 2024 08:35:39 +0900
From: Daniel Palmer <daniel@...f.com>
To: Finn Thain <fthain@...ux-m68k.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, stable@...nel.org, 
	linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] m68k: mvme147: Fix SCSI controller IRQ numbers

Hi all,

On Thu, 3 Oct 2024 at 12:32, Finn Thain <fthain@...ux-m68k.org> wrote:
>
> From: Daniel Palmer <daniel@...f.com>
>
> Sometime long ago the m68k IRQ code was refactored and the interrupt
> numbers for SCSI controller on this board ended up wrong, and it hasn't
> worked since.
>
> The PCC adds 0x40 to the vector for its interrupts so they end up in
> the user interrupt range. Hence, the kernel number should be the kernel
> offset for user interrupt range + the PCC interrupt number.
>
> Cc: Daniel Palmer <daniel@...f.com>
> Cc: stable@...nel.org
> Fixes: 200a3d352cd5 ("[PATCH] m68k: convert VME irq code")
> Signed-off-by: Daniel Palmer <daniel@...f.com>
> Reviewed-by: Finn Thain <fthain@...ux-m68k.org>
> ---

The other part of this that fixes the SCSI driver itself is now merged
and backported to stable branches so it'd be nice to get this merged
too.

Thanks,

Daniel