netdev - Re: [net-next] can: isotp: sanitize CAN ID checks in isotp

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: <20220316080111.s2hlj6krlzcroxh6@pengutronix.de>
Date:   Wed, 16 Mar 2022 09:01:11 +0100
From:   Marc Kleine-Budde <mkl@...gutronix.de>
To:     Oliver Hartkopp <socketcan@...tkopp.net>
Cc:     Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
        syzbot+2339c27f5c66c652843e@...kaller.appspotmail.com,
        linux-can <linux-can@...r.kernel.org>
Subject: Re: [net-next] can: isotp: sanitize CAN ID checks in isotp_bind()

On 16.03.2022 08:53:54, Oliver Hartkopp wrote:
> > Should this go into net/master with stable on Cc or to net-next?
> 
> This patch is for net-next as it won't apply to net/master nor the
> stable trees due to the recent changes in net-next.
> 
> As it contains a Fixes: tag I would send the patch for the stable
> trees when the patch hits Linus' tree and likely Greg would show up
> asking for it.
> 
> I hope that's the most elegant process here?!?

Another option is to port the patch to net/master with the hope that
back porting is easier. Then talk to Jakub and David about the merge
conflict when net/master is merged to net-next/master.

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)