linux-kernel - Re: [PATCH v2] rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE

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: <7670876b.ea0b8.189912c3a92.Coremail.linma@zju.edu.cn>
Date:   Wed, 26 Jul 2023 15:49:02 +0800 (GMT+08:00)
From:   "Lin Ma" <linma@....edu.cn>
To:     "Nikolay Aleksandrov" <razor@...ckwall.org>
Cc:     davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
        pabeni@...hat.com, idosch@...dia.com, lucien.xin@...il.com,
        liuhangbin@...il.com, edwin.peer@...adcom.com, jiri@...nulli.us,
        md.fahad.iqbal.polash@...el.com, anirudh.venkataramanan@...el.com,
        jeffrey.t.kirsher@...el.com, neerav.parikh@...el.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] rtnetlink: let rtnl_bridge_setlink checks
 IFLA_BRIDGE_MODE length

Hi Nikolay,

> 
> Patch looks good now, you should probably remove the extra checks done
> by each driver that are now unnecessary (net-next material). As Hangbin
> commented you should target this fix at -net, with that:
> 
> Acked-by: Nikolay Aleksandrov <razor@...ckwall.org>

Cool, I agree with Hangbin that another patch which removes the redundant
checks in driver is needed.

But I have a simple question. I will send this patch to net one and another
to net-next one. How can I ensure the latter one depends on the former one?
Or should I send a patch series to net-next that contains the former one :)
(I currently choose the method 2 and please let me know if I do this wrong)

Regards
Lin