From: Mark Rutland <mark.rutland@arm.com> To: Marco Elver <elver@google.com> Cc: Kefeng Wang <wangkefeng.wang@huawei.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Joey Gouly <joey.gouly@arm.com> Subject: Re: [PATCH v4] arm64: Enable KCSAN Date: Wed, 15 Dec 2021 09:38:53 +0000 [thread overview] Message-ID: <Ybm3rfq+9bNEX1Rt@FVFF77S0Q05N> (raw) In-Reply-To: <CANpmjNP_M2R9XD8GnCJVTmN17GPOR_5Y3jX8r5AAKcaDRUWJ4A@mail.gmail.com> On Tue, Dec 14, 2021 at 08:11:24PM +0100, Marco Elver wrote: > On Tue, 14 Dec 2021 at 19:24, Mark Rutland <mark.rutland@arm.com> wrote: > > > > Reviewed-by: Mark Rutland <mark.rutland@arm.com> > > Tested-by: Mark Rutland <mark.rutland@arm.com> > > Thanks for taking a look and testing! Thought I'd update you re status > of some of the reports below. :-) Thanks for the pointers below! I'll fold those into a test branch, so that I can soak this under Syzkaller over the holiday break. I've given precise refernces below in case I've misunderstood or missed something. > > * BUG: KCSAN: data-race in mutex_spin_on_owner+0xcc/0x150 > > * BUG: KCSAN: data-race in rwsem_spin_on_owner+0xa8/0x13c > > These are going away, fixes are already in -tip/-next. Cool! I assume that means commits: * c0bed69daf4b6780 ("locking: Make owner_on_cpu() into <linux/sched.h>") from https://lore.kernel.org/r/20211203075935.136808-2-wangkefeng.wang@huawei.com * 4cf75fd4a2545ca4 ("locking: Mark racy reads of owner->on_cpu") from https://lore.kernel.org/r/20211203075935.136808-3-wangkefeng.wang@huawei.com ... in the tip locking/core branch (the head commit of which is currently 5fb6e8cf53b005d2 ("locking/atomic: atomic64: Remove unusable atomic ops")). > > * UBSAN: object-size-mismatch in net/unix/af_unix.c:977:14 > > The UBSAN object-size-mismatch warnings are going away, as > fsanitize=object-size is broken/incomplete as it turns out -- > UBSAN_OBJECT_SIZE will be removed from 5.17: > https://bugzilla.kernel.org/show_bug.cgi?id=214861#c4 I see the relevant patch is: * "[PATCH] ubsan: Remove CONFIG_UBSAN_OBJECT_SIZE" from https://lore.kernel.org/all/20211203235346.110809-1-keescook@chromium.org/ ... and from looking at next-20211214 that's been picked up by Andrew Morton. Thanks, Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com> To: Marco Elver <elver@google.com> Cc: Kefeng Wang <wangkefeng.wang@huawei.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Joey Gouly <joey.gouly@arm.com> Subject: Re: [PATCH v4] arm64: Enable KCSAN Date: Wed, 15 Dec 2021 09:38:53 +0000 [thread overview] Message-ID: <Ybm3rfq+9bNEX1Rt@FVFF77S0Q05N> (raw) In-Reply-To: <CANpmjNP_M2R9XD8GnCJVTmN17GPOR_5Y3jX8r5AAKcaDRUWJ4A@mail.gmail.com> On Tue, Dec 14, 2021 at 08:11:24PM +0100, Marco Elver wrote: > On Tue, 14 Dec 2021 at 19:24, Mark Rutland <mark.rutland@arm.com> wrote: > > > > Reviewed-by: Mark Rutland <mark.rutland@arm.com> > > Tested-by: Mark Rutland <mark.rutland@arm.com> > > Thanks for taking a look and testing! Thought I'd update you re status > of some of the reports below. :-) Thanks for the pointers below! I'll fold those into a test branch, so that I can soak this under Syzkaller over the holiday break. I've given precise refernces below in case I've misunderstood or missed something. > > * BUG: KCSAN: data-race in mutex_spin_on_owner+0xcc/0x150 > > * BUG: KCSAN: data-race in rwsem_spin_on_owner+0xa8/0x13c > > These are going away, fixes are already in -tip/-next. Cool! I assume that means commits: * c0bed69daf4b6780 ("locking: Make owner_on_cpu() into <linux/sched.h>") from https://lore.kernel.org/r/20211203075935.136808-2-wangkefeng.wang@huawei.com * 4cf75fd4a2545ca4 ("locking: Mark racy reads of owner->on_cpu") from https://lore.kernel.org/r/20211203075935.136808-3-wangkefeng.wang@huawei.com ... in the tip locking/core branch (the head commit of which is currently 5fb6e8cf53b005d2 ("locking/atomic: atomic64: Remove unusable atomic ops")). > > * UBSAN: object-size-mismatch in net/unix/af_unix.c:977:14 > > The UBSAN object-size-mismatch warnings are going away, as > fsanitize=object-size is broken/incomplete as it turns out -- > UBSAN_OBJECT_SIZE will be removed from 5.17: > https://bugzilla.kernel.org/show_bug.cgi?id=214861#c4 I see the relevant patch is: * "[PATCH] ubsan: Remove CONFIG_UBSAN_OBJECT_SIZE" from https://lore.kernel.org/all/20211203235346.110809-1-keescook@chromium.org/ ... and from looking at next-20211214 that's been picked up by Andrew Morton. Thanks, Mark. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-15 9:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-11 13:17 [PATCH v4] arm64: Enable KCSAN Kefeng Wang 2021-12-11 13:17 ` Kefeng Wang 2021-12-14 18:24 ` Mark Rutland 2021-12-14 18:24 ` Mark Rutland 2021-12-14 19:11 ` Marco Elver 2021-12-14 19:11 ` Marco Elver 2021-12-15 9:38 ` Mark Rutland [this message] 2021-12-15 9:38 ` Mark Rutland 2021-12-15 4:08 ` Kefeng Wang 2021-12-15 4:08 ` Kefeng Wang 2021-12-14 19:16 ` Catalin Marinas 2021-12-14 19:16 ` Catalin Marinas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=Ybm3rfq+9bNEX1Rt@FVFF77S0Q05N \ --to=mark.rutland@arm.com \ --cc=catalin.marinas@arm.com \ --cc=elver@google.com \ --cc=joey.gouly@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=wangkefeng.wang@huawei.com \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.