Received-SPF: pass (google.com: domain of linux-kernel+bounces-98622-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Mon, 11 Mar 2024 17:30:36 +0800
From: Changbin Du <changbin.du@huawei.com>
To: Marco Elver <elver@google.com>
CC: Changbin Du <changbin.du@huawei.com>, Alexander Potapenko
	<glider@google.com>, Andrew Morton <akpm@linux-foundation.org>,
	<kasan-dev@googlegroups.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [BUG] kmsan: instrumentation recursion problems
Message-ID: <20240311093036.44txy57hvhevybsu@M910t>
References: <20240308043448.masllzeqwht45d4j@M910t>
 <CANpmjNOc4Z6Qy_L3pjuW84BOxoiqXgLC1tWbJuZwRUZqs2ioMA@mail.gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CANpmjNOc4Z6Qy_L3pjuW84BOxoiqXgLC1tWbJuZwRUZqs2ioMA@mail.gmail.com>

On Fri, Mar 08, 2024 at 10:39:15AM +0100, Marco Elver wrote:
> On Fri, 8 Mar 2024 at 05:36, 'Changbin Du' via kasan-dev
> <kasan-dev@googlegroups.com> wrote:
> >
> > Hey, folks,
> > I found two instrumentation recursion issues on mainline kernel.
> >
> > 1. recur on preempt count.
> > __msan_metadata_ptr_for_load_4() -> kmsan_virt_addr_valid() -> preempt_disable() -> __msan_metadata_ptr_for_load_4()
> >
> > 2. recur in lockdep and rcu
> > __msan_metadata_ptr_for_load_4() -> kmsan_virt_addr_valid() -> pfn_valid() -> rcu_read_lock_sched() -> lock_acquire() -> rcu_is_watching() -> __msan_metadata_ptr_for_load_8()
> >
> >
> > Here is an unofficial fix, I don't know if it will generate false reports.
> >
> > $ git show
> > commit 7f0120b621c1cbb667822b0f7eb89f3c25868509 (HEAD -> master)
> > Author: Changbin Du <changbin.du@huawei.com>
> > Date:   Fri Mar 8 20:21:48 2024 +0800
> >
> >     kmsan: fix instrumentation recursions
> >
> >     Signed-off-by: Changbin Du <changbin.du@huawei.com>
> >
> > diff --git a/kernel/locking/Makefile b/kernel/locking/Makefile
> > index 0db4093d17b8..ea925731fa40 100644
> > --- a/kernel/locking/Makefile
> > +++ b/kernel/locking/Makefile
> > @@ -7,6 +7,7 @@ obj-y += mutex.o semaphore.o rwsem.o percpu-rwsem.o
> >
> >  # Avoid recursion lockdep -> sanitizer -> ... -> lockdep.
> >  KCSAN_SANITIZE_lockdep.o := n
> > +KMSAN_SANITIZE_lockdep.o := n
> 
> This does not result in false positives?
>
I saw a lot of reports but seems not related to this.

[    2.742743][    T0] BUG: KMSAN: uninit-value in unwind_next_frame+0x3729/0x48a0
[    2.744404][    T0]  unwind_next_frame+0x3729/0x48a0
[    2.745623][    T0]  arch_stack_walk+0x1d9/0x2a0
[    2.746838][    T0]  stack_trace_save+0xb8/0x100
[    2.747928][    T0]  set_track_prepare+0x88/0x120
[    2.749095][    T0]  __alloc_object+0x602/0xbe0
[    2.750200][    T0]  __create_object+0x3f/0x4e0
[    2.751332][    T0]  pcpu_alloc+0x1e18/0x2b00
[    2.752401][    T0]  mm_init+0x688/0xb20
[    2.753436][    T0]  mm_alloc+0xf4/0x180
[    2.754510][    T0]  poking_init+0x50/0x500
[    2.755594][    T0]  start_kernel+0x3b0/0xbf0
[    2.756724][    T0]  __pfx_reserve_bios_regions+0x0/0x10
[    2.758073][    T0]  x86_64_start_kernel+0x92/0xa0
[    2.759320][    T0]  secondary_startup_64_no_verify+0x176/0x17b


> Does
> KMSAN_ENABLE_CHECKS_lockdep.o := n
> work as well? If it does, that is preferred because it makes sure
> there are no false positives if the lockdep code unpoisons data that
> is passed and used outside lockdep.
> 
> lockdep has a serious impact on performance, and not sanitizing it
> with KMSAN is probably a reasonable performance trade-off.
> 
Disabling checks is not working here. The recursion become this:

__msan_metadata_ptr_for_load_4() -> kmsan_get_metadata() -> virt_to_page_or_null() -> pfn_valid() -> lock_acquire() -> __msan_unpoison_alloca() -> kmsan_get_metadata()

> >  ifdef CONFIG_FUNCTION_TRACER
> >  CFLAGS_REMOVE_lockdep.o = $(CC_FLAGS_FTRACE)
> > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > index b2bccfd37c38..8935cc866e2d 100644
> > --- a/kernel/rcu/tree.c
> > +++ b/kernel/rcu/tree.c
> > @@ -692,7 +692,7 @@ static void rcu_disable_urgency_upon_qs(struct rcu_data *rdp)
> >   * Make notrace because it can be called by the internal functions of
> >   * ftrace, and making this notrace removes unnecessary recursion calls.
> >   */
> > -notrace bool rcu_is_watching(void)
> > +notrace __no_sanitize_memory bool rcu_is_watching(void)
> 
> For all of these, does __no_kmsan_checks instead of __no_sanitize_memory work?
> Again, __no_kmsan_checks (function-only counterpart to
> KMSAN_ENABLE_CHECKS_.... := n) is preferred if it works as it avoids
> any potential false positives that would be introduced by not
> instrumenting.
> 
This works because it is not unpoisoning local variables.

> >  {
> >         bool ret;
> >
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index 9116bcc90346..33aa4df8fd82 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -5848,7 +5848,7 @@ static inline void preempt_latency_start(int val)
> >         }
> >  }
> >
> > -void preempt_count_add(int val)
> > +void __no_sanitize_memory preempt_count_add(int val)
> >  {
> >  #ifdef CONFIG_DEBUG_PREEMPT
> >         /*
> > @@ -5880,7 +5880,7 @@ static inline void preempt_latency_stop(int val)
> >                 trace_preempt_on(CALLER_ADDR0, get_lock_parent_ip());
> >  }
> >
> > -void preempt_count_sub(int val)
> > +void __no_sanitize_memory preempt_count_sub(int val)
> >  {
> >  #ifdef CONFIG_DEBUG_PREEMPT
> >
> >
> > --
> > Cheers,
> > Changbin Du

-- 
Cheers,
Changbin Du