[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240112105836.mVtRB2us@linutronix.de>
Date: Fri, 12 Jan 2024 11:58:36 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: kernel test robot <lkp@...el.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
oe-kbuild-all@...ts.linux.dev, Boqun Feng <boqun.feng@...il.com>,
Daniel Borkmann <daniel@...earbox.net>,
Eric Dumazet <edumazet@...gle.com>,
Frederic Weisbecker <frederic@...nel.org>,
Ingo Molnar <mingo@...hat.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Waiman Long <longman@...hat.com>, Will Deacon <will@...nel.org>
Subject: Re: [PATCH net-next 04/24] net: Use nested-BH locking for
napi_alloc_cache.
On 2023-12-16 12:43:23 [+0800], kernel test robot wrote:
> Hi Sebastian,
Hi,
> >> net/core/skbuff.c:302:38: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct local_lock_t [usertype] *l @@ got struct local_lock_t [noderef] __percpu * @@
updated the guard definition for that.
Thanks for the report.
Sebastian
Powered by blists - more mailing lists