Re: [PATCH 1/1] net: ipv6: flowlabel: defer exclusive option free until RCU teardown

[Yuan Tan <yuantan098@gmail.com>]

On 3/31/2026 1:52 AM, Eric Dumazet wrote:
> On Tue, Mar 31, 2026 at 1:34 AM Ren Wei <n05ec@lzu.edu.cn> wrote:
>> From: Zhengchuan Liang <zcliangcn@gmail.com>
>>
>> `ip6fl_seq_show()` walks the global flowlabel hash under the seq-file
>> RCU read-side lock and prints `fl->opt->opt_nflen` when an option block
>> is present.
> Some points :
>
> Please do not CC security@ if you submit a public patch, there is
> absolutely no reason for it.
>
> Please do not resend the same version within 24 hours; this creates noise.
> Your patch wasn't lost; we have many patch reviews and similar bugs to address.
>
> Thank you.

We sincerely apologize for the confusion caused by our previous email. Previously, when we sent reports and patches to the security list, we were advised that patches should be submitted to netdev@ for public review. To follow this, we are now sending the full vulnerability details to security@ while additionally submitting the patches to netdev@. Please let us know if this is the correct way to handle such cases.

Regarding the CC list, could you provide further guidance on who we should include? Currently, we are CCing everyone suggested by get_maintainer.pl because we previously received feedback about missing relevant maintainers. For public mailing lists, we should only including netdev@. Should we be more selective?

Finally, regarding our tags, our team has a clear division of labor—some focus on finding vulnerabilities, others on fixing them, followed by an internal review and testing before a dedicated member handles community outreach.

We welcome any guidance and will improve our upcoming patches accordingly. To be honest, we are currently a bit uncertain about the exact workflow the community prefers, and we are eager to align our process with your expectations.