[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200605041218.GD2667@sol.localdomain>
Date: Thu, 4 Jun 2020 21:12:18 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Ritesh Harjani <riteshh@...ux.ibm.com>
Cc: adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com,
tytso@....edu,
syzbot <syzbot+aed048f49c59eb997737@...kaller.appspotmail.com>
Subject: Re: linux-next test error: BUG: using smp_processor_id() in
preemptible [ADDR] code: systemd-rfkill/6728
On Thu, Jun 04, 2020 at 09:02:20PM -0700, Eric Biggers wrote:
> Introduced by:
>
> commit 42f56b7a4a7db127a9d281da584152dc3d525d25
> Author: Ritesh Harjani <riteshh@...ux.ibm.com>
> Date: Wed May 20 12:10:34 2020 +0530
>
> ext4: mballoc: introduce pcpu seqcnt for freeing PA to improve ENOSPC handling
>
Hmm, syzbot reported this several times already. Marking it as a duplicate
of the report where the discussion happened:
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: syz-fuzzer/6792
- Eric
Powered by blists - more mailing lists