From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 3970E3C09E2 for ; Thu, 4 Jun 2026 19:30:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780601403; cv=none; b=U7XJ1NMrjvCH7lBJ6YojQbRg8od5fe6G285dIh4SpVelEUjOnRVNrLPPWiabkOLcdUZSm/xKNOvZWptl3IogmGKnwbHXZEe+tk/MZk38UHJBHUpDlu3+zshHsk/LFj0XkUAZ8JhLnRxHYahTXHA4v5D6gZcD4kv6FWR8GqmPCtg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780601403; c=relaxed/simple; bh=XN1Ho16Ogq64r7uCxHlFu/LlXxPUEuQbmoUbIlCtMQM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=OZ0LQE3Z/Bi7S/UFVNGje/OQ1vZP2Qddxu8vB49togVcW6/JSfHlajb9uNOsp0zi/9L/NnchFxH5m0TNJL1MN1IByAQ6PLeC8bz3dwn7mwNxKqqknvPRVLJfARhrmJsPGiLy/upHMECyENJG+11aF85+C3+VJr7ocaCFW0khX3Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=OlBPjeio; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="OlBPjeio" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 27F101F00893; Thu, 4 Jun 2026 19:30:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780601401; bh=mozolD+uuWfpaCykYRgW9OWCwEdnV36HeAtr6qQH09o=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=OlBPjeio7Z9cZIxWOnb3vmoGbncDrq2EyHn7RNdx4QamMfQJP4NE+kmz34eaT+HpB KizvoiH7J4x4V7BuQ4cikMEqyyzPh8RJREAxSs4kMEF0eEy1voN+A0rh4jGXtH4wek 9dDFZnCAE7fT9dBdhppZUdGibRJcDvIJFR5HVxeo89HiQBfYJ0G8hvInKiAhRcBCWh R/0H5sJUrzIj3Q6K6D8h/qhwJq/3RrVSLI+JCjOIU7i3aZAb97J7SXXgtZAPCbBXyp T0VRSEoXJ6NhQ3m3BQ6X3Csi4MrdgKlINpFORG0rK/Bsdr0/ebS5rAfFtb0QoIWPG3 gm4d3oRNhq68Q== From: Thomas Gleixner To: Zijing Yin , Anna-Maria Behnsen , Frederic Weisbecker Cc: Zijing Yin , linux-kernel@vger.kernel.org Subject: Re: UBSAN: invalid-load in __remove_hrtimer In-Reply-To: <20260604171043.995130-1-yzjaurora@gmail.com> References: <20260604171043.995130-1-yzjaurora@gmail.com> Date: Thu, 04 Jun 2026 21:29:58 +0200 Message-ID: <87qzmm3xzd.ffs@fw13> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Thu, Jun 04 2026 at 10:10, Zijing Yin wrote: > Fuzzing v7.1-rc1 (98878ed91b68) with a customized syzkaller on a > KASAN+UBSAN build, I hit the UBSAN invalid-load below in Please validate that this still is the case with the latest v7.1-rc6 or ideally with the head of Linus tree. > UBSAN: invalid-load in kernel/time/hrtimer.c:1147:14 > load of value 255 is not a valid value for type 'bool' (aka '_Bool') That's memory corruption from some unknown place unrelated to the hrtimer subsystem, which acts only as the messenger. Which becomes obvious due to this: > Oops: general protection fault, probably for non-canonical address 0xf1a7c288031699ea: 0000 [#1] KASAN NOPTI Thanks, tglx