netdev - RE: [PATCH] can: rcar_canfd: rcar_canfd_handle_global_receive(): fix IRQ storm on global FIFO receive

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: <OS0PR01MB59222BA2B1CAA6CDA9B4137486369@OS0PR01MB5922.jpnprd01.prod.outlook.com>
Date:   Tue, 1 Nov 2022 07:59:30 +0000
From:   Biju Das <biju.das.jz@...renesas.com>
To:     Pavel Machek <pavel@...x.de>
CC:     Wolfgang Grandegger <wg@...ndegger.com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        Marc Kleine-Budde <mkl@...gutronix.de>,
        Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@...renesas.com>,
        Sasha Levin <sashal@...nel.org>,
        "linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Chris Paterson <Chris.Paterson2@...esas.com>,
        "linux-renesas-soc@...r.kernel.org" 
        <linux-renesas-soc@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [PATCH] can: rcar_canfd: rcar_canfd_handle_global_receive(): fix
 IRQ storm on global FIFO receive

Hi Pavel,

Thanks for the feedback.

> Subject: Re: [PATCH] can: rcar_canfd:
> rcar_canfd_handle_global_receive(): fix IRQ storm on global FIFO
> receive
> 
> Hi!
> 
> > Fixes: dd3bd23eb438 ("can: rcar_canfd: Add Renesas R-Car CAN FD
> > driver")
> > Suggested-by: Marc Kleine-Budde <mkl@...gutronix.de>
> > Signed-off-by: Biju Das <biju.das.jz@...renesas.com>
> > Link:
> > https://lore.kernel.org/all/20221025155657.1426948-2-
> biju.das.jz@...re
> > nesas.com
> > Cc: stable@...r.kernel.org#5.15.y
> > [mkl: adjust commit message]
> 
> I got 7 or so copies of this, with slightly different Cc: lines.

I followed option 1 mentioned in [1]

[1] https://www.kernel.org/doc/html/v5.10/process/stable-kernel-rules.html


> 
> AFAICT this is supposed to be stable kernel submission. In such case,
> I'd expect [PATCH 4.14, 4.19, 5.10] in the subject line, and original
> sign-off block from the mainline patch.

OK. Maybe [1] needs updating.

> 
> OTOH if it has Fixes tag (and it does) or Cc: stable (it has both),
> normally there's no need to do separate submission to stable, as Greg
> handles these automatically?

I got merge conflict mails for 4.9, 4.14, 4.19, 5.4, 5.10 and 5.15 stable.
I thought, I need to fix the conflicts and resend. Am I missing anything?? Please let me know.

Cheers,
biju