From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Stefan Wahren <stefan.wahren@i2se.com>, regressions@lists.linux.dev
Cc: bpf@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
jpalus@fastmail.com
Subject: Re: [BUG] null pointer dereference when loading bpf_preload on Raspberry Pi
Date: Sun, 4 Sep 2022 11:28:53 +0200 [thread overview]
Message-ID: <d610de0d-d0f9-6c1f-93e1-b408109b861f@leemhuis.info> (raw)
In-Reply-To: <d58ed1a8-99d5-c45a-975f-85b71a1f3928@i2se.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-04 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 22:22 [BUG] null pointer dereference when loading bpf_preload on Raspberry Pi Stefan Wahren
2022-06-13 11:12 ` Russell King (Oracle)
2022-06-13 14:42 ` Stefan Wahren
2022-06-15 6:11 ` Stefan Wahren
2022-06-15 8:31 ` Peter Robinson
2022-06-15 9:57 ` Stefan Wahren
2022-06-15 10:07 ` Peter Robinson
2022-06-19 17:06 ` Thorsten Leemhuis
2022-09-03 14:17 ` Stefan Wahren
2022-09-03 14:44 ` Stefan Wahren
2022-09-04 9:28 ` Thorsten Leemhuis [this message]
2022-07-04 12:42 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d610de0d-d0f9-6c1f-93e1-b408109b861f@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bpf@vger.kernel.org \
--cc=jpalus@fastmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=regressions@lists.linux.dev \
--cc=stefan.wahren@i2se.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).