linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentin Schneider <valentin.schneider@arm.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, LKP <lkp@lists.01.org>,
	lkp@intel.com
Subject: Re: 5b9f8ff7b3 ("sched/debug: Output SD flag names rather than .."): [  320.831182] BUG: KASAN: double-free or invalid-free in sd_ctl_doflags
Date: Tue, 17 Nov 2020 17:21:26 +0000	[thread overview]
Message-ID: <jhjr1orx5k9.mognet@arm.com> (raw)
In-Reply-To: <20201117003123.GB3723@shao2-debian>


Hi,

On 17/11/20 00:31, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit 5b9f8ff7b320a34af3dbcf04edb40d9b04f22f4a
> Author:     Valentin Schneider <valentin.schneider@arm.com>
> AuthorDate: Mon Aug 17 12:29:52 2020 +0100
> Commit:     Ingo Molnar <mingo@kernel.org>
> CommitDate: Wed Aug 19 10:49:48 2020 +0200
>
>     sched/debug: Output SD flag names rather than their values
>     
>     Decoding the output of /proc/sys/kernel/sched_domain/cpu*/domain*/flags has
>     always been somewhat annoying, as one needs to go fetch the bit -> name
>     mapping from the source code itself. This encoding can be saved in a script
>     somewhere, but that isn't safe from flags being added, removed or even
>     shuffled around.
>     
>     What matters for debugging purposes is to get *which* flags are set in a
>     given domain, their associated value is pretty much meaningless.
>     
>     Make the sd flags debug file output flag names.
>     
>     Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
>     Signed-off-by: Ingo Molnar <mingo@kernel.org>
>     Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
>     Link: https://lore.kernel.org/r/20200817113003.20802-7-valentin.schneider@arm.com
>
> 65c5e25316  sched/topology: Verify SD_* flags setup when sched_debug is on
> 5b9f8ff7b3  sched/debug: Output SD flag names rather than their values
> 3cea11cd5e  Linux 5.10-rc2
> +-------------------------------------------------+------------+------------+-----------+
> |                                                 | 65c5e25316 | 5b9f8ff7b3 | v5.10-rc2 |
> +-------------------------------------------------+------------+------------+-----------+
> | boot_successes                                  | 824        | 523        | 322       |
> | boot_failures                                   | 491        | 331        | 145       |
> | WARNING:at_mm/usercopy.c:#usercopy_warn         | 439        | 292        | 143       |
> | RIP:usercopy_warn                               | 439        | 292        | 143       |
> | INFO:rcu_sched_self-detected_stall_on_CPU       | 38         | 22         |           |
> | RIP:iov_iter_copy_from_user_atomic              | 26         | 15         |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c0:#] | 6          | 3          |           |
> | Kernel_panic-not_syncing                        | 39         | 23         |           |
> | RIP:ftrace_likely_update                        | 33         | 19         |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c6:#] | 5          | 3          |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c4:#] | 10         | 4          |           |
> | WARNING:kernel_stack                            | 3          | 1          |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c2:#] | 6          | 2          |           |
> | RIP:init_numa_balancing                         | 1          |            |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c5:#] | 5          | 2          |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c7:#] | 3          | 3          |           |
> | RIP:default_idle                                | 2          | 2          |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c3:#] | 4          | 4          |           |
> | BUG:kernel_hang_in_boot_stage                   | 8          | 1          | 1         |
> | WARNING:at_fs/read_write.c:#vfs_copy_file_range | 1          |            |           |
> | RIP:vfs_copy_file_range                         | 1          |            |           |
> | invoked_oom-killer:gfp_mask=0x                  | 0          | 1          |           |
> | Mem-Info                                        | 0          | 2          |           |
> | BUG:KASAN:double-free_or_invalid-free_in_s      | 0          | 10         | 1         |
> | RIP:_raw_spin_unlock_irq                        | 0          | 1          |           |
> | BUG:kernel_reboot-without-warning_in_test_stage | 0          | 1          |           |
> | BUG:soft_lockup-CPU##stuck_for#s![trinity-c1:#] | 0          | 1          |           |
> | canonical_address#:#[##]                        | 0          | 1          |           |
> | RIP:write_port                                  | 0          | 1          |           |
> +-------------------------------------------------+------------+------------+-----------+
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
>

This has been fixed by Colin, and is in v5.10-rc4:

8d4d9c7b4333 ("sched/debug: Fix memory corruption caused by multiple small reads of flags")

Thanks.

      reply	other threads:[~2020-11-17 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  0:31 5b9f8ff7b3 ("sched/debug: Output SD flag names rather than .."): [ 320.831182] BUG: KASAN: double-free or invalid-free in sd_ctl_doflags kernel test robot
2020-11-17 17:21 ` Valentin Schneider [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=jhjr1orx5k9.mognet@arm.com \
    --to=valentin.schneider@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=mingo@kernel.org \
    --cc=rong.a.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;
as well as URLs for NNTP newsgroup(s).