From: Jan Kara <jack@suse.cz>
To: kernel test robot <lkp@intel.com>
Cc: Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [fsnotify] 9b93f33105: WARNING:missing_R10_value_at__fsnotify_parent/0x
Date: Fri, 23 Oct 2020 17:13:29 +0200 [thread overview]
Message-ID: <20201023151329.GA9119@quack2.suse.cz> (raw)
In-Reply-To: <20201023003842.GC31092@shao2-debian>
Hello,
On Fri 23-10-20 08:38:42, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: 9b93f33105f5f9bd3d016ff870eb6000c9d89eff ("fsnotify: send event with parent/name info to sb/mount/non-dir marks")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
>
> in testcase: will-it-scale
> version: will-it-scale-x86_64-b695a1b-1_20201007
> with following parameters:
>
> nr_task: 192
> mode: process
> test: read2
> cpufreq_governor: performance
> ucode: 0x11
>
...
> [ 117.801209] perf version 5.9.rc8.gc85fb28b6f99
> [ 117.801219]
> [ 182.458747] perf: interrupt took too long (2668 > 2500),perf: interrupt took too long (4516 > 4352), lowering kernel.perf_event_max_sample_rate to 44000
> lowering kernel.perf_event_max_sample_rperf: interrupt took too long (5950 > 5645), lowering kernel.perf_event_max_sample_rate to 33000
> ate to 74000
> perf: interrupt took too long (7658 > 7437), lowering kernel.perf_event_max_sample_rate to 26000
> [ 182.502968] perf: interrupt took too long (7658 > 7437), lowering kernel.perf_event_max_sample_rate to 26000
> [ 182.525840] perf: interrupt took too long (9889 > 9572), lowering kernel.perf_event_max_sample_rate to 20000
> f_event_max_sample_rate to 12000
> [ 182.560905] perf: interrupt took too long (21827 > 20585), lowering kernel.perf_event_max_sample_rate to 9000
> [ 182.609949] perf: interrupt took too long (30149 > 27283), lowering kernel.perf_event_max_sample_rate to 6000
> [ 182.622872] perf: interrupt took too long (38986 > 37686), lowering kernel.perf_event_max_sample_rate to 5000
> [ 182.672850] perf: interrupt took too long (50874 > 48732), lowering kernel.perf_event_max_sample_rate to 3000
> [ 182.732849] perf: interrupt took too long (63885 > 63592), lowering kernel.perf_event_max_sample_rate to 3000
> [ 182.751847] perf: interrupt took too long (80901 > 79856), lowering kernel.perf_event_max_sample_rate to 2000
> [ 188.527603] WARNING: missing R10 value at __fsnotify_parent+0x25/0x280
OK, that's an unwinder warning but we don't do anything special in
__fsnotify_parent(). Let's CC x86 guys if they have idea what's going on.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-10-23 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 0:38 [fsnotify] 9b93f33105: WARNING:missing_R10_value_at__fsnotify_parent/0x kernel test robot
2020-10-23 15:13 ` Jan Kara [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=20201023151329.GA9119@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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