From: Andrew Morton <akpm@linux-foundation.org>
To: "Zhang, Qiang1" <qiang1.zhang@intel.com>
Cc: "ryabinin.a.a@gmail.com" <ryabinin.a.a@gmail.com>,
"glider@google.com" <glider@google.com>,
"andreyknvl@gmail.com" <andreyknvl@gmail.com>,
"dvyukov@google.com" <dvyukov@google.com>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v2] kasan: Fix sleeping function called from invalid context on RT kernel
Date: Mon, 18 Apr 2022 21:20:42 -0700 [thread overview]
Message-ID: <20220418212042.ae77c3c7ad51d95e59d6f78a@linux-foundation.org> (raw)
In-Reply-To: <PH0PR11MB5880FAABCE50894AE6A77528DAF19@PH0PR11MB5880.namprd11.prod.outlook.com>
On Sat, 16 Apr 2022 02:47:43 +0000 "Zhang, Qiang1" <qiang1.zhang@intel.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?
prev parent reply other threads:[~2022-04-19 4:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 13:46 Zqiang
2022-04-01 16:06 ` Dmitry Vyukov
2022-04-01 23:14 ` Zhang, Qiang1
2022-04-02 7:03 ` Dmitry Vyukov
2022-04-06 4:39 ` Zhang, Qiang1
2022-04-15 18:34 ` Andrew Morton
2022-04-16 2:47 ` Zhang, Qiang1
2022-04-19 4:20 ` Andrew Morton [this message]
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=20220418212042.ae77c3c7ad51d95e59d6f78a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiang1.zhang@intel.com \
--cc=ryabinin.a.a@gmail.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox