linux-kernel - Re:Re: [PATCH linux next] net: neigh: use kfree_skb_reason() in neigh_resolve

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: <20250520184032009VEzfxkkFmbQjfs0qCJ5QB@zte.com.cn>
Date: Tue, 20 May 2025 18:40:32 +0800 (CST)
From: <jiang.kun2@....com.cn>
To: <kuniyu@...zon.com>
Cc: <davem@...emloft.net>, <edumazet@...gle.com>, <fan.yu9@....com.cn>,
        <gnaaman@...venets.com>, <he.peilin@....com.cn>, <horms@...nel.org>,
        <kuba@...nel.org>, <kuniyu@...zon.com>, <leitao@...ian.org>,
        <linux-kernel@...r.kernel.org>, <lizetao1@...wei.com>,
        <netdev@...r.kernel.org>, <pabeni@...hat.com>, <qiu.yutan@....com.cn>,
        <tu.qiang35@....com.cn>, <wang.yaxin@....com.cn>,
        <xu.xin16@....com.cn>, <yang.yang29@....com.cn>,
        <ye.xingchen@....com.cn>, <zhang.yunkai@....com.cn>
Subject: Re:Re: [PATCH linux next] net: neigh: use kfree_skb_reason() in neigh_resolve_output()

>Is there any reason you don't change neigh_connected_output() ?
>
>
>If you respin, please specify net-next and the patch version in
>
>Subject: [PATCH v2 net-next] net: neighbour: ...
>

Thank you for your feedback.
I notice that most commits related to kfree_skb_reason() involve changes 
within the scope of a single function, which aligns with the meaning of 
the commit titles. I consider this approach appropriate as it facilitates 
both modification and traceability. Following this approach, I will submit 
another new patch to specifically modify neigh_connected_output().
<div class="zcontentRow"><div style="font-size:14px;font-family:微软雅黑,Microsoft YaHei;line-height:1.5"><div style="line-height:1.5">&gt;Is there any reason you don't change neigh_connected_output() ?</div><div style="line-height:1.5">&gt;</div><div style="line-height:1.5">&gt;</div><div style="line-height:1.5">&gt;If you respin, please specify net-next and the patch version in</div><div style="line-height:1.5">&gt;</div><div style="line-height:1.5">&gt;Subject: [PATCH v2 net-next] net: neighbour: ...</div><div style="line-height:1.5">&gt;</div><div style="line-height:1.5"><br></div><div style="line-height:1.5">Thank you for your feedback.</div><div style="line-height:1.5">I notice that most commits related to kfree_skb_reason() involve changes&nbsp;</div><div style="line-height:1.5">within the scope of a single function, which aligns with the meaning of&nbsp;</div><div style="line-height:1.5">the commit titles. I consider this approach appropriate as it facilitates&nbsp;</div><div style="line-height:1.5">both modification and traceability. Following this approach, I will submit&nbsp;</div><div style="line-height:1.5">another new patch to specifically modify neigh_connected_output().</div></div><br><br><br><br><br></div>