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: <a93e5967-026a-186d-2bf0-5628631b9e28@leemhuis.info> Date: Thu, 7 Jul 2022 12:17:16 +0200 From: Thorsten Leemhuis <regressions@...mhuis.info> To: Florian Westphal <fw@...len.de>, netfilter-devel@...r.kernel.org Cc: regressions@...ts.linux.dev, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>, Kajetan Puchalski <kajetan.puchalski@....com>, Will Deacon <will@...nel.org> Subject: Re: [PATCH nf v3] netfilter: conntrack: fix crash due to confirmed bit load reordering On 06.07.22 16:50, Florian Westphal wrote: > Kajetan Puchalski reports crash on ARM, with backtrace of: > > [...] > Cc: Peter Zijlstra <peterz@...radead.org> > Reported-by: Kajetan Puchalski <kajetan.puchalski@....com> > Diagnosed-by: Will Deacon <will@...nel.org> > Fixes: 719774377622 ("netfilter: conntrack: convert to refcount_t api") > Signed-off-by: Florian Westphal <fw@...len.de> If you need to respin this patch for one reason or another, could you do me a favor and add proper 'Link:' tags pointing to all reports about this issue? e.g. like this: Link: https://lore.kernel.org/all/Yr7WTfd6AVTQkLjI@e126311.manchester.arm.com/ These tags are considered important by Linus[1] and others, as they allow anyone to look into the backstory weeks or years from now. That is why they should be placed in cases like this, as Documentation/process/submitting-patches.rst and Documentation/process/5.Posting.rst explain in more detail. I care personally, because these tags make my regression tracking efforts a whole lot easier, as they allow my tracking bot 'regzbot' to automatically connect reports with patches posted or committed to fix tracked regressions. [1] see for example: https://lore.kernel.org/all/CAHk-=wjMmSZzMJ3Xnskdg4+GGz=5p5p+GSYyFBTh0f-DgvdBWg@mail.gmail.com/ https://lore.kernel.org/all/CAHk-=wgs38ZrfPvy=nOwVkVzjpM3VFU1zobP37Fwd_h9iAD5JQ@mail.gmail.com/ https://lore.kernel.org/all/CAHk-=wjxzafG-=J8oT30s7upn4RhBs6TX-uVFZ5rME+L5_DoJA@mail.gmail.com/ Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.
Powered by blists - more mailing lists