From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
rcu@vger.kernel.org, rostedt@goodmis.org
Subject: [GIT PULL] scftorture changes for v6.4
Date: Thu, 24 Aug 2023 15:06:20 -0700 [thread overview]
Message-ID: <79cb1ec7-08ec-40d2-bbb4-ce40b684f1a4@paulmck-laptop> (raw)
Hello, Linus,
Once the merge window opens, please pull these scftorture changes:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/scftorture.2023.08.15a
# HEAD: 3f68f9c822ebe208f961ab0402e49a10465278ca: scftorture: Add CONFIG_PREEMPT_DYNAMIC=n to NOPREEMPT scenario (2023-07-14 15:02:57 -0700)
----------------------------------------------------------------
smp_call_function torture-test updates for v6.6
This pull request prevents some memory-exhaustion false-postitive failures
in scftorture testing.
----------------------------------------------------------------
Paul E. McKenney (4):
torture: Scale scftorture memory based on number of CPUs
scftorture: Forgive memory-allocation failure if KASAN
scftorture: Pause testing after memory-allocation failure
scftorture: Add CONFIG_PREEMPT_DYNAMIC=n to NOPREEMPT scenario
kernel/scftorture.c | 12 +++++++++---
tools/testing/selftests/rcutorture/bin/torture.sh | 4 +++-
tools/testing/selftests/rcutorture/configs/scf/NOPREEMPT | 2 ++
3 files changed, 14 insertions(+), 4 deletions(-)
next reply other threads:[~2023-08-24 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 22:06 Paul E. McKenney [this message]
2023-08-24 23:07 ` Linus Torvalds
2023-08-24 23:23 ` Paul E. McKenney
2023-08-28 22:15 ` pr-tracker-bot
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=79cb1ec7-08ec-40d2-bbb4-ce40b684f1a4@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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: 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
all inboxes | Powered by JetHome®