[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251028075218.aw9YABrW@linutronix.de>
Date: Tue, 28 Oct 2025 08:52:18 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Yonghong Song <yonghong.song@...ux.dev>
Cc: Sahil Chandna <chandna.sahil@...il.com>,
syzbot+b0cff308140f79a9c4cb@...kaller.appspotmail.com,
andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
daniel@...earbox.net, eddyz87@...il.com, haoluo@...gle.com,
john.fastabend@...il.com, jolsa@...nel.org, kpsingh@...nel.org,
linux-kernel@...r.kernel.org, listout@...tout.xyz,
martin.lau@...ux.dev, netdev@...r.kernel.org, sdf@...ichev.me,
song@...nel.org, syzkaller-bugs@...glegroups.com,
linux-rt-devel@...ts.linux.dev
Subject: Re: [syzbot] [bpf?] WARNING in bpf_bprintf_prepare (3)
On 2025-10-27 20:45:25 [-0700], Yonghong Song wrote:
> This should work, but local lock disable interrupts which could have
> negative side effects on the system. We don't want this.
> That is the reason we have 3 nested level for bpf_bprintf_buffers.
>
> Please try my above preempt_disalbe/enable() solution.
I meant to look into this yesterday but got distracted with other
things. I try to take a look.
Sebastian
Powered by blists - more mailing lists