On 2021-02-23 14:53:40 [+0100], Juri Lelli wrote:
>
> So, I'm a bit confused and I'm very likely missing details (still
> digesting the seqprop_ magic), but write_seqcount_being() has
>
> if (seqprop_preemptible(s))
> preempt_disable();
>
> which in this case (no lock associated) is
On Tue, Feb 23, 2021 at 02:53:40PM +0100, Juri Lelli wrote:
> On 23/02/21 12:00, Sebastian Andrzej Siewior wrote:
> > On 2021-02-23 11:49:07 [+0100], Juri Lelli wrote:
> > > Hi,
> > Hi,
> >
> > > I'm seeing the following splat right after boot (or during late boot
> > > phases) with v5.11-rt7
On 23/02/21 12:00, Sebastian Andrzej Siewior wrote:
> On 2021-02-23 11:49:07 [+0100], Juri Lelli wrote:
> > Hi,
> Hi,
>
> > I'm seeing the following splat right after boot (or during late boot
> > phases) with v5.11-rt7 (LOCKDEP enabled).
> …
> > [ 85.273588] WARNING: CPU: 5 PID: 1416 at
On 2021-02-23 11:49:07 [+0100], Juri Lelli wrote:
> Hi,
Hi,
> I'm seeing the following splat right after boot (or during late boot
> phases) with v5.11-rt7 (LOCKDEP enabled).
…
> [ 85.273588] WARNING: CPU: 5 PID: 1416 at include/linux/seqlock.h:271
> nft_counter_eval+0x95/0x130 [nft_counter]
…
Hi,
I'm seeing the following splat right after boot (or during late boot
phases) with v5.11-rt7 (LOCKDEP enabled).
[ 85.273583] [ cut here ]
[ 85.273588] WARNING: CPU: 5 PID: 1416 at include/linux/seqlock.h:271
nft_counter_eval+0x95/0x130 [nft_counter]
[ 85.273600]
5 matches
Mail list logo