On 5/18/22 1:28 PM, Marek Szyprowski wrote:
> On 16.05.2022 19:39, bh1scw@xxxxxxxxx wrote:
>> From: Fanjun Kong <bh1scw@xxxxxxxxx>
>>
>> spin_lock_irq/spin_unlock_irq contains preempt_disable/enable().
>> Which can serve as RCU read-side critical region, so remove
>> rcu_read_lock/unlock().
>>
>> Signed-off-by: Fanjun Kong <bh1scw@xxxxxxxxx>
>
> This patch landed in today's linux next-20220518 as commit 77c570a1ea85
> ("blk-cgroup: Remove unnecessary rcu_read_lock/unlock()").
>
> Unfortunately it triggers the following warning on ARM64 based Raspberry
> Pi 4B board:>
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at block/blk-cgroup.c:301 blkg_create+0x398/0x4e0
Should this use rcu_read_lock_any_held() rather than rcu_read_lock_held()?
--
Jens Axboe
