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]
Message-ID: <20250321104557426O89NLhm9SSuAOJwRDq75V@zte.com.cn>
Date: Fri, 21 Mar 2025 10:45:57 +0800 (CST)
From: <tang.dongxing@....com.cn>
To: <horms@...nel.org>
Cc: <krzk@...nel.org>, <davem@...emloft.net>, <feng.wei8@....com.cn>,
        <shao.mingyin@....com.cn>, <xie.ludan@....com.cn>,
        <edumazet@...gle.com>, <kuba@...nel.org>, <pabeni@...hat.com>,
        <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <yang.guang5@....com.cn>, <yang.yang29@....com.cn>,
        <ye.xingchen@....com.cn>, <xu.xin16@....com.cn>
Subject: Re: [PATCH] net: atm: use sysfs_emit_at() instead of scnprintf()

>On Mon, Mar 17, 2025 at 05:09:02PM +0800, tang.dongxing@....com.cn wrote:
>> >On 17/03/2025 08:51, tang.dongxing@....com.cn wrote:> From: TangDongxing <tang.dongxing@....com.cn>
>> >> 
>> >> Follow the advice in Documentation/filesystems/sysfs.rst:
>> >> show() should only use sysfs_emit() or sysfs_emit_at() when formatting
>> >> the value to be returned to user space.
>> >> 
>> >> Signed-off-by: Tang Dongxing <tang.dongxing@....com.cn>Dear ZTE,
>> >
>> >Can you slow down? You sent a bunch of emails with similar issues which
>> >means that dozen of maintainers will deal with the same issues
>> >independently. This looks like another vivo or huawei style submission,
>> >leading to bugs sneaked via flood of patches.
>> >
>> >First, fix the name used in the SoB (see submitting patches) to match
>> >Latin transcription.
>> >
>> >Second, use proper SoB chain, see submitting patches.
>> >
>> >Third, really, really be sure that what you send is correct. You already
>> >got quite responses, but you still keep sending patches.
>> >
>> >Fourth, respond to received feedback instead of flooding us with more of
>> >this!
>> 
>> Dear Krzysztof,
>> Thank you for your feedback. I apologize for my previous submissions.
>> Regarding the issues you've pointed out:
>> I will correct the name used in the SoB to ensure it matches the Latin transcription as required.
>> I will double-check my work before sending any further updates.
>> I appreciate your guidance and will follow the submission guidelines more carefully going forward. If you have any further advice or resources to help me improve my submissions, I would be grateful for your input.
>> Best regards, 
>> Tang Dongxing
>
>Thanks Tang Dongxing,
>
>Further to Krzystof's comments: please coordinate with your colleague
>Xie Ludan who has also posted a patch in this area.
>
>  https://lore.kernel.org/all/20250317152933756kWrF1Y_e-2EKtrR_GGegq@zte.com.cn/
>
>It will be much easier for review if there is a single patch
>that addresses these issues for ATM.
>
>Also, please consider reading the following guidance on processes
>for the networking subsystem of the Linux kernel. These are similar
>but different to other subsystems.
>
>  https://docs.kernel.org/process/maintainer-netdev.html

Dear SimonHroman,

Thank you for your guidance. I have contacted Xie Ludan,
we recommend that the community review be based on the https://lore.kernel.org/all/20250317152933756kWrF1Y_e-2EKtrR_GGegq@zte.com.cn/
I will carefully read the the networking subsystem guidance before sending any further updates.

Best regard,

Tang Dongxing





Original


From: horms <horms@...nel.org>
To: Tang Dongxing10346056;
Cc: krzk <krzk@...nel.org>;davem <davem@...emloft.net>;Feng Wei10332721;Shao Mingyin10345846;Xie Ludan00297061;edumazet <edumazet@...gle.com>;kuba <kuba@...nel.org>;pabeni <pabeni@...hat.com>;netdev <netdev@...r.kernel.org>;linux-kernel <linux-kernel@...r.kernel.org>;Yang Guang10296924;Yang Yang10192021;Ye Xingchen10329245;Xu Xin10311587;
Date: 2025/03/20 19:44
Subject: Re: [PATCH] net: atm: use sysfs_emit_at() instead of scnprintf()

On Mon, Mar 17, 2025 at 05:09:02PM +0800, tang.dongxing@....com.cn wrote:
> >On 17/03/2025 08:51, tang.dongxing@....com.cn wrote:> From: TangDongxing <tang.dongxing@....com.cn> 
> >>  
> >> Follow the advice in Documentation/filesystems/sysfs.rst:
> >> show() should only use sysfs_emit() or sysfs_emit_at() when formatting
> >> the value to be returned to user space.
> >>  
> >> Signed-off-by: Tang Dongxing <tang.dongxing@....com.cn>Dear ZTE,
> > 
> >Can you slow down? You sent a bunch of emails with similar issues which
> >means that dozen of maintainers will deal with the same issues
> >independently. This looks like another vivo or huawei style submission,
> >leading to bugs sneaked via flood of patches.
> > 
> >First, fix the name used in the SoB (see submitting patches) to match
> >Latin transcription.
> > 
> >Second, use proper SoB chain, see submitting patches.
> > 
> >Third, really, really be sure that what you send is correct. You already
> >got quite responses, but you still keep sending patches.
> > 
> >Fourth, respond to received feedback instead of flooding us with more of
> >this!
>  
> Dear Krzysztof,
> Thank you for your feedback. I apologize for my previous submissions.
> Regarding the issues you've pointed out:
> I will correct the name used in the SoB to ensure it matches the Latin transcription as required.
> I will double-check my work before sending any further updates.
> I appreciate your guidance and will follow the submission guidelines more carefully going forward. If you have any further advice or resources to help me improve my submissions, I would be grateful for your input.
> Best regards,  
> Tang Dongxing
 
Thanks Tang Dongxing,
 
Further to Krzystof's comments: please coordinate with your colleague
Xie Ludan who has also posted a patch in this area.
 
  https://lore.kernel.org/all/20250317152933756kWrF1Y_e-2EKtrR_GGegq@zte.com.cn/
 
It will be much easier for review if there is a single patch
that addresses these issues for ATM.
 
Also, please consider reading the following guidance on processes
for the networking subsystem of the Linux kernel. These are similar
but different to other subsystems.
 
  https://docs.kernel.org/process/maintainer-netdev.html
 
--  
pw-bot: changes-requested
<div class="zcontentRow"><p>&gt;On Mon, Mar 17, 2025 at 05:09:02PM +0800, tang.dongxing@....com.cn wrote:</p><p>&gt;&gt; &gt;On 17/03/2025 08:51, tang.dongxing@....com.cn wrote:&gt; From: TangDongxing &lt;tang.dongxing@....com.cn&gt;</p><p>&gt;&gt; &gt;&gt;&nbsp;</p><p>&gt;&gt; &gt;&gt; Follow the advice in Documentation/filesystems/sysfs.rst:</p><p>&gt;&gt; &gt;&gt; show() should only use sysfs_emit() or sysfs_emit_at() when formatting</p><p>&gt;&gt; &gt;&gt; the value to be returned to user space.</p><p>&gt;&gt; &gt;&gt;&nbsp;</p><p>&gt;&gt; &gt;&gt; Signed-off-by: Tang Dongxing &lt;tang.dongxing@....com.cn&gt;Dear ZTE,</p><p>&gt;&gt; &gt;</p><p>&gt;&gt; &gt;Can you slow down? You sent a bunch of emails with similar issues which</p><p>&gt;&gt; &gt;means that dozen of maintainers will deal with the same issues</p><p>&gt;&gt; &gt;independently. This looks like another vivo or huawei style submission,</p><p>&gt;&gt; &gt;leading to bugs sneaked via flood of patches.</p><p>&gt;&gt; &gt;</p><p>&gt;&gt; &gt;First, fix the name used in the SoB (see submitting patches) to match</p><p>&gt;&gt; &gt;Latin transcription.</p><p>&gt;&gt; &gt;</p><p>&gt;&gt; &gt;Second, use proper SoB chain, see submitting patches.</p><p>&gt;&gt; &gt;</p><p>&gt;&gt; &gt;Third, really, really be sure that what you send is correct. You already</p><p>&gt;&gt; &gt;got quite responses, but you still keep sending patches.</p><p>&gt;&gt; &gt;</p><p>&gt;&gt; &gt;Fourth, respond to received feedback instead of flooding us with more of</p><p>&gt;&gt; &gt;this!</p><p>&gt;&gt;&nbsp;</p><p>&gt;&gt; Dear Krzysztof,</p><p>&gt;&gt; Thank you for your feedback. I apologize for my previous submissions.</p><p>&gt;&gt; Regarding the issues you've pointed out:</p><p>&gt;&gt; I will correct the name used in the SoB to ensure it matches the Latin transcription as required.</p><p>&gt;&gt; I will double-check my work before sending any further updates.</p><p>&gt;&gt; I appreciate your guidance and will follow the submission guidelines more carefully going forward. If you have any further advice or resources to help me improve my submissions, I would be grateful for your input.</p><p>&gt;&gt; Best regards,&nbsp;</p><p>&gt;&gt; Tang Dongxing</p><p>&gt;</p><p>&gt;Thanks Tang Dongxing,</p><p>&gt;</p><p>&gt;Further to Krzystof's comments: please coordinate with your colleague</p><p>&gt;Xie Ludan who has also posted a patch in this area.</p><p>&gt;</p><p>&gt;&nbsp; https://lore.kernel.org/all/20250317152933756kWrF1Y_e-2EKtrR_GGegq@zte.com.cn/</p><p>&gt;</p><p>&gt;It will be much easier for review if there is a single patch</p><p>&gt;that addresses these issues for ATM.</p><p>&gt;</p><p>&gt;Also, please consider reading the following guidance on processes</p><p>&gt;for the networking subsystem of the Linux kernel. These are similar</p><p>&gt;but different to other subsystems.</p><p>&gt;</p><p>&gt;&nbsp; https://docs.kernel.org/process/maintainer-netdev.html</p><p><br></p><p>Dear SimonHroman,</p><p><br></p><p>Thank you for your guidance. I have contacted Xie Ludan,</p><p>we recommend that the community review be based on the https://lore.kernel.org/all/20250317152933756kWrF1Y_e-2EKtrR_GGegq@zte.com.cn/</p><p>I will carefully read the the networking subsystem guidance before sending any further updates.</p><p><br></p><p>Best regard,</p><p><br></p><p>Tang Dongxing</p><p style="font-size:14px;font-family:微软雅黑,Microsoft YaHei;"><br></p><p style="font-size:14px;font-family:微软雅黑,Microsoft YaHei;"><br></p><p style="font-size:14px;font-family:微软雅黑,Microsoft YaHei;"><br></p><p style="font-size:14px;font-family:微软雅黑,Microsoft YaHei;"><br></p><div class="zhistoryRow" style="display:block"><div class="zhistoryDes" style="width: 100%; height: 28px; line-height: 28px; background-color: #E0E5E9; color: #1388FF; text-align: center;">Original</div><div id="zwriteHistoryContainer"><div class="control-group zhistoryPanel"><div class="zhistoryHeader" style="padding: 8px; background-color: #F5F6F8;"><div><strong>From:&nbsp;</strong><span class="zreadUserName">horms &lt;horms@...nel.org&gt;</span></div><div><strong>To:&nbsp;</strong><span class="zreadUserName" style="display: inline;">Tang Dongxing10346056;</span></div><div><strong>Cc:&nbsp;</strong><span class="zreadUserName" style="display: inline;">krzk &lt;krzk@...nel.org&gt;;</span><span class="zreadUserName" style="display: inline;">davem &lt;davem@...emloft.net&gt;;</span><span class="zreadUserName" style="display: inline;">Feng Wei10332721;</span><span class="zreadUserName" style="display: inline;">Shao Mingyin10345846;</span><span class="zreadUserName" style="display: inline;">Xie Ludan00297061;</span><span class="zreadUserName" style="display: inline;">edumazet &lt;edumazet@...gle.com&gt;;</span><span class="zreadUserName" style="display: inline;">kuba &lt;kuba@...nel.org&gt;;</span><span class="zreadUserName" style="display: inline;">pabeni &lt;pabeni@...hat.com&gt;;</span><span class="zreadUserName" style="display: inline;">netdev &lt;netdev@...r.kernel.org&gt;;</span><span class="zreadUserName" style="display: inline;">linux-kernel &lt;linux-kernel@...r.kernel.org&gt;;</span><span class="zreadUserName" style="display: inline;">Yang Guang10296924;</span><span class="zreadUserName" style="display: inline;">Yang Yang10192021;</span><span class="zreadUserName" style="display: inline;">Ye Xingchen10329245;</span><span class="zreadUserName" style="display: inline;">Xu Xin10311587;</span></div><div><strong>Date:&nbsp;</strong><span class="">2025/03/20 19:44</span></div><div><strong>Subject:&nbsp;</strong><span class="zreadTitle"><strong>Re: [PATCH] net: atm: use sysfs_emit_at() instead of scnprintf()</strong></span></div></div><div class="zhistoryContent">On&nbsp;Mon,&nbsp;Mar&nbsp;17,&nbsp;2025&nbsp;at&nbsp;05:09:02PM&nbsp;+0800,&nbsp;tang.dongxing@....com.cn&nbsp;wrote:<br>&gt;&nbsp;&gt;On&nbsp;17/03/2025&nbsp;08:51,&nbsp;tang.dongxing@....com.cn&nbsp;wrote:&gt;&nbsp;From:&nbsp;TangDongxing&nbsp;&lt;tang.dongxing@....com.cn&gt; <br>&gt;&nbsp;&gt;&gt;&nbsp; <br>&gt;&nbsp;&gt;&gt;&nbsp;Follow&nbsp;the&nbsp;advice&nbsp;in&nbsp;Documentation/filesystems/sysfs.rst:<br>&gt;&nbsp;&gt;&gt;&nbsp;show()&nbsp;should&nbsp;only&nbsp;use&nbsp;sysfs_emit()&nbsp;or&nbsp;sysfs_emit_at()&nbsp;when&nbsp;formatting<br>&gt;&nbsp;&gt;&gt;&nbsp;the&nbsp;value&nbsp;to&nbsp;be&nbsp;returned&nbsp;to&nbsp;user&nbsp;space.<br>&gt;&nbsp;&gt;&gt;&nbsp; <br>&gt;&nbsp;&gt;&gt;&nbsp;Signed-off-by:&nbsp;Tang&nbsp;Dongxing&nbsp;&lt;tang.dongxing@....com.cn&gt;Dear&nbsp;ZTE,<br>&gt;&nbsp;&gt; <br>&gt;&nbsp;&gt;Can&nbsp;you&nbsp;slow&nbsp;down?&nbsp;You&nbsp;sent&nbsp;a&nbsp;bunch&nbsp;of&nbsp;emails&nbsp;with&nbsp;similar&nbsp;issues&nbsp;which<br>&gt;&nbsp;&gt;means&nbsp;that&nbsp;dozen&nbsp;of&nbsp;maintainers&nbsp;will&nbsp;deal&nbsp;with&nbsp;the&nbsp;same&nbsp;issues<br>&gt;&nbsp;&gt;independently.&nbsp;This&nbsp;looks&nbsp;like&nbsp;another&nbsp;vivo&nbsp;or&nbsp;huawei&nbsp;style&nbsp;submission,<br>&gt;&nbsp;&gt;leading&nbsp;to&nbsp;bugs&nbsp;sneaked&nbsp;via&nbsp;flood&nbsp;of&nbsp;patches.<br>&gt;&nbsp;&gt; <br>&gt;&nbsp;&gt;First,&nbsp;fix&nbsp;the&nbsp;name&nbsp;used&nbsp;in&nbsp;the&nbsp;SoB&nbsp;(see&nbsp;submitting&nbsp;patches)&nbsp;to&nbsp;match<br>&gt;&nbsp;&gt;Latin&nbsp;transcription.<br>&gt;&nbsp;&gt; <br>&gt;&nbsp;&gt;Second,&nbsp;use&nbsp;proper&nbsp;SoB&nbsp;chain,&nbsp;see&nbsp;submitting&nbsp;patches.<br>&gt;&nbsp;&gt; <br>&gt;&nbsp;&gt;Third,&nbsp;really,&nbsp;really&nbsp;be&nbsp;sure&nbsp;that&nbsp;what&nbsp;you&nbsp;send&nbsp;is&nbsp;correct.&nbsp;You&nbsp;already<br>&gt;&nbsp;&gt;got&nbsp;quite&nbsp;responses,&nbsp;but&nbsp;you&nbsp;still&nbsp;keep&nbsp;sending&nbsp;patches.<br>&gt;&nbsp;&gt; <br>&gt;&nbsp;&gt;Fourth,&nbsp;respond&nbsp;to&nbsp;received&nbsp;feedback&nbsp;instead&nbsp;of&nbsp;flooding&nbsp;us&nbsp;with&nbsp;more&nbsp;of<br>&gt;&nbsp;&gt;this!<br>&gt;&nbsp; <br>&gt;&nbsp;Dear&nbsp;Krzysztof,<br>&gt;&nbsp;Thank&nbsp;you&nbsp;for&nbsp;your&nbsp;feedback.&nbsp;I&nbsp;apologize&nbsp;for&nbsp;my&nbsp;previous&nbsp;submissions.<br>&gt;&nbsp;Regarding&nbsp;the&nbsp;issues&nbsp;you've&nbsp;pointed&nbsp;out:<br>&gt;&nbsp;I&nbsp;will&nbsp;correct&nbsp;the&nbsp;name&nbsp;used&nbsp;in&nbsp;the&nbsp;SoB&nbsp;to&nbsp;ensure&nbsp;it&nbsp;matches&nbsp;the&nbsp;Latin&nbsp;transcription&nbsp;as&nbsp;required.<br>&gt;&nbsp;I&nbsp;will&nbsp;double-check&nbsp;my&nbsp;work&nbsp;before&nbsp;sending&nbsp;any&nbsp;further&nbsp;updates.<br>&gt;&nbsp;I&nbsp;appreciate&nbsp;your&nbsp;guidance&nbsp;and&nbsp;will&nbsp;follow&nbsp;the&nbsp;submission&nbsp;guidelines&nbsp;more&nbsp;carefully&nbsp;going&nbsp;forward.&nbsp;If&nbsp;you&nbsp;have&nbsp;any&nbsp;further&nbsp;advice&nbsp;or&nbsp;resources&nbsp;to&nbsp;help&nbsp;me&nbsp;improve&nbsp;my&nbsp;submissions,&nbsp;I&nbsp;would&nbsp;be&nbsp;grateful&nbsp;for&nbsp;your&nbsp;input.<br>&gt;&nbsp;Best&nbsp;regards,&nbsp; <br>&gt;&nbsp;Tang&nbsp;Dongxing<br> <br>Thanks&nbsp;Tang&nbsp;Dongxing,<br> <br>Further&nbsp;to&nbsp;Krzystof's&nbsp;comments:&nbsp;please&nbsp;coordinate&nbsp;with&nbsp;your&nbsp;colleague<br>Xie&nbsp;Ludan&nbsp;who&nbsp;has&nbsp;also&nbsp;posted&nbsp;a&nbsp;patch&nbsp;in&nbsp;this&nbsp;area.<br> <br>&nbsp;&nbsp;https://lore.kernel.org/all/20250317152933756kWrF1Y_e-2EKtrR_GGegq@zte.com.cn/<br> <br>It&nbsp;will&nbsp;be&nbsp;much&nbsp;easier&nbsp;for&nbsp;review&nbsp;if&nbsp;there&nbsp;is&nbsp;a&nbsp;single&nbsp;patch<br>that&nbsp;addresses&nbsp;these&nbsp;issues&nbsp;for&nbsp;ATM.<br> <br>Also,&nbsp;please&nbsp;consider&nbsp;reading&nbsp;the&nbsp;following&nbsp;guidance&nbsp;on&nbsp;processes<br>for&nbsp;the&nbsp;networking&nbsp;subsystem&nbsp;of&nbsp;the&nbsp;Linux&nbsp;kernel.&nbsp;These&nbsp;are&nbsp;similar<br>but&nbsp;different&nbsp;to&nbsp;other&nbsp;subsystems.<br> <br>&nbsp;&nbsp;https://docs.kernel.org/process/maintainer-netdev.html<br> <br>--&nbsp; <br>pw-bot:&nbsp;changes-requested</div></div></div></div><p><br></p></div>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ