[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20220418212042.ae77c3c7ad51d95e59d6f78a@linux-foundation.org>
Date: Mon, 18 Apr 2022 21:20:42 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Zhang, Qiang1" <qiang1.zhang@...el.com>
Cc: "ryabinin.a.a@...il.com" <ryabinin.a.a@...il.com>,
"glider@...gle.com" <glider@...gle.com>,
"andreyknvl@...il.com" <andreyknvl@...il.com>,
"dvyukov@...gle.com" <dvyukov@...gle.com>,
"bigeasy@...utronix.de" <bigeasy@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH v2] kasan: Fix sleeping function called from invalid
context on RT kernel
On Sat, 16 Apr 2022 02:47:43 +0000 "Zhang, Qiang1" <qiang1.zhang@...el.com> wrote:
> >Note that it incorporates the changes from your https://lkml.kernel.org/r/20220414025925.2423818-1-qiang1.zhang@intel.com
> >
> >btw, how are we supposed to test PREEMPT_RT builds? I had to patch arch/Kconfig.
>
> The attachment is a config file and I test with linux-5.17.y-rt branch (https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git), I have been tested.
OK, but it's a problem that we're adding CONFIG_PREEMPT_RT code to the
mainline kernel without providing for it to be at least compile-tested.
Sebastian, is there something we can do here to increase the coverage
testing?
Powered by blists - more mailing lists