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] [day] [month] [year] [list]

Date:   Tue, 1 Nov 2022 14:32:02 +0100
From:   "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Biju Das <biju.das.jz@...renesas.com>,
        Pavel Machek <pavel@...x.de>,
        Wolfgang Grandegger <wg@...ndegger.com>,
        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

On Tue, Nov 01, 2022 at 07:36:20PM +0700, Bagas Sanjaya wrote:
> On 11/1/22 14:59, Biju Das wrote:
> >> 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.
> 
> The documentation says (in this case the third option applies):
> 
> > Send the patch, after verifying that it follows the above rules, to> stable@...r.kernel.org. You must note the upstream commit ID in the
> > changelog of your submission, as well as the kernel version you wish
> > it to be applied to.
> 
> It doesn't specify how to mark desired target branch, unfortunately.

And that's fine, the submitter did the right thing here and gave me all
of the information that I need.  Please do not confuse people, there is
nothing wrong with the submission as-is.

thanks,

greg k-h