From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 49177259CAB for ; Tue, 29 Jul 2025 07:27:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1753774080; cv=none; b=a/3LI2LEQZFTeJXw2r8DPMW8WNGwcZR2/Mfy1Jfaik/pXk9wuZzmTasB24j+F3hYC4SJQLD+xUNUt1pPVi4+DxF1EvvoBSHzpM6dC+DGQbqWzc4N5Yo5PcR5I7YljKPTyAGmQltYk8/12FCHJhE6izNhJVU0PGdPg3jXTo49uQU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1753774080; c=relaxed/simple; bh=cjMbHXuWdh0ckiTqMrJMeOkJfSlpMF+5IDejF4OdABs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=ZttLWOYEoYVUkrB1MidhKdd/GjsFgL+csoWvzYCZa5Kr5XpN3NM+Z0Zahb4f0TcNN3S/Uyjw5ntES8dKBrlHsLzs9Kz0tYPFi2q3AHFnbgQKXdJMgq+PDYJOpYNNKf4aXDGqckBs6iX7bh7Tt1pn0pFttSEx07VnNJQPwsYdbpM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=eK4w4i7l; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=8P2C9jOT; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="eK4w4i7l"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="8P2C9jOT" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1753774077; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8bBYSTZpcRwKvIkblTZvAnTSurmf8yAiPann+WMyjBQ=; b=eK4w4i7lYj7DJFTnZu+4u/xtfibAeUVwOCGmq28M6sv/FW7HGnKxpF0hv3K1NhBMU5JGO8 yd6Bni0OIPp+rssxWbW6f8aEPOKLfQw9xomuwPvK+5fU3fItddhPKJQVMhOEdSMvtSWRfg V3VamnBKS9UxD7I2ejvhfuj5jXwmdsX2XnSnyz6j9WairOFbJM3BoAkCB/6WLXrUROM4aK QgtjFS8cQI3auT/EBLlOHx7iy45BKHBxxu0IwSEgrurubfawpexT1Sk3Lp20R6qvjs8OaV 8LmVxZ5Azpl1uBJCELw0h0kjfkSvyNpWWitpc3UTx1/Qvgq/L/zIBAff6LL4BA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1753774077; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8bBYSTZpcRwKvIkblTZvAnTSurmf8yAiPann+WMyjBQ=; b=8P2C9jOTMPv3/SiXxbOC2HqnDfEuJZYCBPU5j0I5WryKLddPUv4BpvbMwSrbtQDpDb6WG2 mUr6nKY0LXmtDzBA== To: Oliver Sang Cc: Peter Zijlstra , oe-lkp@lists.linux.dev, lkp@intel.com, linux-kernel@vger.kernel.org, x86@kernel.org, Sebastian Andrzej Siewior , linux-mm@kvack.org, ltp@lists.linux.it, oliver.sang@intel.com Subject: Re: [tip:locking/futex] [futex] 56180dd20c: BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c In-Reply-To: References: <202507231021.dcf24373-lkp@intel.com> <87a54usty4.ffs@tglx> <87seikp94v.ffs@tglx> Date: Tue, 29 Jul 2025 09:27:56 +0200 Message-ID: <87wm7ro3r7.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Oliver! On Tue, Jul 29 2025 at 08:22, Oliver Sang wrote: > On Fri, Jul 25, 2025 at 05:45:04PM +0200, Thomas Gleixner wrote: >> Can you please enable CONFIG_PREEMPT_TRACER and add >> >> 'trace_event=preemptirq:preempt_disable,preemptirq:preempt_enable ftrace_dump_on_oops' >> >> to the kernel command line. The latter will dump the recorded >> preempt_enable/disable events and we can pinpoint the function which is >> responsible for that. > > the config with CONFIG_PREEMPT_TRACER enabled is attached as > config-6.16.0-rc5-00002-g56180dd20c19 > > by this config, we still see random > WARNING:at_kernel/sched/core.c:#preempt_count_sub ... > but bot seems not be able to capture other new dmesg stats. Ah. The tracer does not dump on warnings by default. You need 'panic_on_warn' on the command line as well. Forgot about that earlier. Thanks, tglx