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: <CANn89iJ7JZp2mtcL912SGzq90wKH0rR=X+2vPuinTnMdTsMvQA@mail.gmail.com> Date: Mon, 22 May 2023 20:57:16 +0200 From: Eric Dumazet <edumazet@...gle.com> To: SeongJae Park <sj@...nel.org> Cc: Kuniyuki Iwashima <kuniyu@...zon.com>, davem@...emloft.net, kuba@...nel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, nmanthey@...zon.de, pabeni@...hat.com, ptyadav@...zon.de, willemb@...gle.com Subject: Re: [PATCH net] net: fix skb leak in __skb_tstamp_tx() On Mon, May 22, 2023 at 7:33 PM SeongJae Park <sj@...nel.org> wrote: > Sorry for continuing adding noises, but seems the process is, or will be, > changed by to the mainline commit dbbe7c962c3a8 ("docs: networking: drop > special stable handling"). Whoever backported the patch because it had a Fixes: tag will do the same if another patch also has a Fixes: tag. I personally prefer Fixes: very precise tags to weak ones.
Powered by blists - more mailing lists