| 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
| ||
|
Message-ID: <20250722165841838ou4ZoIujZCCgIG2HAu1T8@zte.com.cn>
Date: Tue, 22 Jul 2025 16:58:41 +0800 (CST)
From: <wang.yaxin@....com.cn>
To: <krzk@...nel.org>
Cc: <jiang.kun2@....com.cn>, <yang.yang29@....com.cn>,
<akpm@...ux-foundation.org>, <xu.xin16@....com.cn>,
<bbonev@...uan.org>, <linux-kernel@...r.kernel.org>,
<bsingharora@...il.com>
Subject: Re: [PATCH linux next] MAINTAINERS: add maintainers for delaytop
>> @@ -19524,6 +19524,16 @@ S: Maintained
>> F: include/linux/delayacct.h
>> F: kernel/delayacct.c
>>
>> +TASK DELAY MONITORING TOOLS
>> +M: Andrew Morton <akpm@...ux-foundation.org>
>> +M: Wang Yaxin <wang.yaxin@....com.cn>
>
>
>There were no contributions from above address. Not a single
>contribution. Not a single review, not a single message or comment. If
>the person wants to review, why reviewing did not happen so far?
Hi Krzysztof,
Thank you for your feedback. I completely understand your concerns about
the maintainer role, and I’d like to provide some context to clarify the
situation.
1) delaytop contributions
Delaytop is used to observe system-wide latency top-n tasks, which helps
in locating latency-related system performance issues.
As Andrew mentioned, delaytop is indeed a new module currently only in
mm.git, which is why there are no related patches in mainline yet.
The related patches are as follows:
https://lore.kernel.org/all/20250619211843633h05gWrBDMFkEH6xAVm_5y@zte.com.cn/
https://lore.kernel.org/all/20250710135451340_5pOgpIFi0M5AE7H44W1D@zte.com.cn/
2) latency-related contributions
I’ve also contributed to latency monitoring in the past (e.g., max latency patches),
showing a continued interest in this area.
https://lore.kernel.org/all/20241203164848805CS62CQPQWG9GLdQj2_BxS@zte.com.cn/
https://lore.kernel.org/all/20241220173105906EOdsPhzjMLYNJJBqgz1ga@zte.com.cn/
3) maintainer role intent
Since the module is new, we recognize that broader community review and adoption
will take time, and we’re committed to supporting that process.
>> +M: Fan Yu <fan.yu9@....com.cn>
>
>And from here just one patchset not even related to delaytop.
>
>So combining above it is really surprising that you want to maintain
>this part.
The development of delaytop (including the initial patches) was a collaborative effort,
as reflected in the Co-developed-by tags. Applying to be the maintainer is to ensure
the long-term evolution of delaytop, while also making it easier for other developers to CC us.
I’d be happy to address any further questions or suggestions. Thank you for your time and consideration!
Yaxin
Thanks
<div class="zcontentRow"><p>>> @@ -19524,6 +19524,16 @@ S: Maintained</p><p>>> F: include/linux/delayacct.h</p><p>>> F: kernel/delayacct.c</p><p>>> </p><p>>> +TASK DELAY MONITORING TOOLS</p><p>>> +M: Andrew Morton <akpm@...ux-foundation.org></p><p>>> +M: Wang Yaxin <wang.yaxin@....com.cn></p><p>></p><p>></p><p>>There were no contributions from above address. Not a single</p><p>>contribution. Not a single review, not a single message or comment. If</p><p>>the person wants to review, why reviewing did not happen so far?</p><p><br></p><p>Hi Krzysztof,</p><p>Thank you for your feedback. I completely understand your concerns about</p><p>the maintainer role, and I’d like to provide some context to clarify the</p><p>situation.</p><p><br></p><p>1) delaytop contributions</p><p>Delaytop is used to observe system-wide latency top-n tasks, which helps</p><p>in locating latency-related system performance issues. </p><p>As Andrew mentioned, delaytop is indeed a new module currently only in</p><p>mm.git, which is why there are no related patches in mainline yet.</p><p>The related patches are as follows: </p><p>https://lore.kernel.org/all/20250619211843633h05gWrBDMFkEH6xAVm_5y@zte.com.cn/</p><p>https://lore.kernel.org/all/20250710135451340_5pOgpIFi0M5AE7H44W1D@zte.com.cn/</p><p><br></p><p>2) latency-related contributions</p><p>I’ve also contributed to latency monitoring in the past (e.g., max latency patches),</p><p>showing a continued interest in this area.</p><p>https://lore.kernel.org/all/20241203164848805CS62CQPQWG9GLdQj2_BxS@zte.com.cn/</p><p>https://lore.kernel.org/all/20241220173105906EOdsPhzjMLYNJJBqgz1ga@zte.com.cn/</p><p><br></p><p>3) maintainer role intent</p><p>Since the module is new, we recognize that broader community review and adoption</p><p>will take time, and we’re committed to supporting that process.</p><p><br></p><p>>> +M: Fan Yu <fan.yu9@....com.cn></p><p>></p><p>>And from here just one patchset not even related to delaytop.</p><p>></p><p>>So combining above it is really surprising that you want to maintain</p><p>>this part.</p><p><br></p><p>The development of delaytop (including the initial patches) was a collaborative effort,</p><p>as reflected in the Co-developed-by tags. Applying to be the maintainer is to ensure</p><p>the long-term evolution of delaytop, while also making it easier for other developers to CC us. </p><p><br></p><p>I’d be happy to address any further questions or suggestions. Thank you for your time and consideration! </p><p><br></p><p>Yaxin</p><p>Thanks</p></div>
Powered by blists - more mailing lists