From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B22217E for ; Sun, 4 Sep 2022 09:29:08 +0000 (UTC) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1oUlw0-00077B-BR; Sun, 04 Sep 2022 11:28:56 +0200 Message-ID: Date: Sun, 4 Sep 2022 11:28:53 +0200 Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 Content-Language: en-US, de-DE To: Stefan Wahren , regressions@lists.linux.dev Cc: bpf@vger.kernel.org, Linux ARM , jpalus@fastmail.com References: <56ffb198-8c93-1ec2-0b5e-9441e96359de@leemhuis.info> <76951173-ce4e-adda-e80e-7c313725e937@i2se.com> From: Thorsten Leemhuis Subject: Re: [BUG] null pointer dereference when loading bpf_preload on Raspberry Pi In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1662283748;f65f2eb0; X-HE-SMSGID: 1oUlw0-00077B-BR On 03.09.22 16:44, Stefan Wahren wrote: > Am 03.09.22 um 16:17 schrieb Stefan Wahren: >> >> Am 19.06.22 um 19:06 schrieb Thorsten Leemhuis: >>> [TLDR: I'm adding this regression report to the list of tracked >>> regressions; all text from me you find below is based on a few templates >>> paragraphs you might have encountered already already in similar form.] >> >> as reported by Jan on Bugzilla [1] the issue has been resolved by >> >> e2dcac2f58f5 ("BPF: Fix potential bad pointer dereference in >> bpf_sys_bpf()") >> >> I can confirm the fix. > > sorry missed the link. > > [1] - https://bugzilla.kernel.org/show_bug.cgi?id=216105 > >> #regzbot fixed-by: |e2dcac2f58f5 Sorry, I'm totally behind with tracking the progress for some regressions because I'm busy preparing three talks :-/ Many thx for letting me know! FWIW, this is how you mail looked like here: ``` |I can confirm the fix. | |#regzbot fixed-by: |e2dcac2f58f5 || """ Regzbot ignored it, as the "#" has to be the first character in a new paragraph. And the "|" before e2dcac2f58f5 would have confused it as well. No worries, happens, that is easily fixed up: #regzbot fixed-by: e2dcac2f58f5 But I wanted to tell you, as it's not the first time you tried to interact with regzbot in a way that failed. I suspect you mailer does something odd. But as I said: no worries, things like that happen. :-D Ciao, Thorsten