From: K Prateek Nayak <kprateek.nayak@amd.com>
To: kernel test robot <oliver.sang@intel.com>,
Xiao Feng via B4 Relay <devnull+xiaofeng5.xiaomi.com@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <aubrey.li@linux.intel.com>,
<yu.c.chen@intel.com>, <ltp@lists.linux.it>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Juri Lelli" <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
"Lorenzo Stoakes" <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
"Vlastimil Babka" <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Kees Cook <kees@kernel.org>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
"Thomas Gleixner" <tglx@kernel.org>, <linux-mm@kvack.org>,
Xiao Feng <xiaofeng5@xiaomi.com>
Subject: Re: [PATCH] sched/fork: Fix timer_slack_ns inheritance for RT tasks
Date: Thu, 28 May 2026 10:54:23 +0530 [thread overview]
Message-ID: <b79c3933-495a-43d2-a68c-4e25386c9a5f@amd.com> (raw)
In-Reply-To: <202605281011.2ba77cc3-lkp@intel.com>
Hello Oliver,
Thank you for the test!
On 5/28/2026 10:20 AM, kernel test robot wrote:
> Suite: syscalls-05
> ──────────────────
>
> ...
>
> ^[[1;37mprctl02: ^[[0m^[[1;32mpass^[[0m | ^[[1;33mtainted^[[0m (0.011s)
> ^[[1;37mprctl08: ^[[0m^[[1;31mfail^[[0m | ^[[1;33mtainted^[[0m (0.011s) <---
I think we are failing here
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/prctl/prctl08.c#L86
for:
{check_inherit_timerslack, 70000, 70000, "Child process"}
This checks if the default timerslack is set to the Parent's timerslack
at the time of fork and prctl(PR_SET_TIMERSLACK, 0) in the child process
expects the timer slack to go back that inherited value.
With this patch, instead of inheriting it, we are resetting it at 50us
at the time of fork. Since this is documented in man page, I believe the
test is correct and this will indeed be a behavior change.
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2026-05-28 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 13:07 Xiao Feng via B4 Relay
2026-05-20 14:57 ` K Prateek Nayak
2026-05-28 4:50 ` kernel test robot
2026-05-28 5:24 ` K Prateek Nayak [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=b79c3933-495a-43d2-a68c-4e25386c9a5f@amd.com \
--to=kprateek.nayak@amd.com \
--cc=akpm@linux-foundation.org \
--cc=aubrey.li@linux.intel.com \
--cc=bsegall@google.com \
--cc=david@kernel.org \
--cc=devnull+xiaofeng5.xiaomi.com@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=felix.moessbauer@siemens.com \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--cc=vbabka@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=xiaofeng5@xiaomi.com \
--cc=yu.c.chen@intel.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
all inboxes | Powered by JetHome®