All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
	kernel test robot <rong.a.chen@intel.com>
Cc: linux-clk@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Sylwester Nawrocki <snawrocki@kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Lukasz Luba <lukasz.luba@arm.com>, 0day robot <lkp@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org
Subject: Re: [clk] a2499eff4b: BUG:kernel_NULL_pointer_dereference,address
Date: Tue, 18 Aug 2020 20:13:33 -0700	[thread overview]
Message-ID: <159780681339.334488.10402512224012716827@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200811084943.GC7488@shao2-debian>

Quoting kernel test robot (2020-08-11 01:49:44)
> Greeting,
> 
> FYI, we noticed the following commit (built with gcc-9):
> 
> commit: a2499eff4b30a85d56e4466e6ca4746c72a347c6 ("[PATCH v2] clk: samsung: Keep top BPLL mux on Exynos542x enabled")
> url: https://github.com/0day-ci/linux/commits/Marek-Szyprowski/clk-samsung-Keep-top-BPLL-mux-on-Exynos542x-enabled/20200807-213239
> base: https://git.kernel.org/cgit/linux/kernel/git/clk/linux.git clk-next
> 
> in testcase: trinity
> with following parameters:
> 
>         runtime: 300s
> 
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/projects/trinity/
> 
> 
> on test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 16G

Cool robot. But this doesn't look related to the patch at all?

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: lkp@lists.01.org
Subject: Re: [clk] a2499eff4b: BUG:kernel_NULL_pointer_dereference, address
Date: Tue, 18 Aug 2020 20:13:33 -0700	[thread overview]
Message-ID: <159780681339.334488.10402512224012716827@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200811084943.GC7488@shao2-debian>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

Quoting kernel test robot (2020-08-11 01:49:44)
> Greeting,
> 
> FYI, we noticed the following commit (built with gcc-9):
> 
> commit: a2499eff4b30a85d56e4466e6ca4746c72a347c6 ("[PATCH v2] clk: samsung: Keep top BPLL mux on Exynos542x enabled")
> url: https://github.com/0day-ci/linux/commits/Marek-Szyprowski/clk-samsung-Keep-top-BPLL-mux-on-Exynos542x-enabled/20200807-213239
> base: https://git.kernel.org/cgit/linux/kernel/git/clk/linux.git clk-next
> 
> in testcase: trinity
> with following parameters:
> 
>         runtime: 300s
> 
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/projects/trinity/
> 
> 
> on test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 16G

Cool robot. But this doesn't look related to the patch at all?

  reply	other threads:[~2020-08-19  3:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200807133152eucas1p1d83611a984f5c5d875192d08e2f5711f@eucas1p1.samsung.com>
2020-08-07 13:31 ` [PATCH v2] clk: samsung: Keep top BPLL mux on Exynos542x enabled Marek Szyprowski
2020-08-10  2:58   ` Chanwoo Choi
2020-08-11  8:49   ` [clk] a2499eff4b: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2020-08-11  8:49     ` kernel test robot
2020-08-19  3:13     ` Stephen Boyd [this message]
2020-08-19  3:13       ` [clk] a2499eff4b: BUG:kernel_NULL_pointer_dereference, address Stephen Boyd
2020-08-20  5:03       ` [clk] a2499eff4b: BUG:kernel_NULL_pointer_dereference,address Rong Chen
2020-08-20  5:03         ` [clk] a2499eff4b: BUG:kernel_NULL_pointer_dereference, address Rong Chen
2020-08-11 11:31   ` [PATCH v2] clk: samsung: Keep top BPLL mux on Exynos542x enabled Sylwester Nawrocki
2020-08-19  3:12     ` Stephen Boyd
2020-08-19  3:14   ` Stephen Boyd
2020-08-23 10:12     ` Sylwester Nawrocki
2020-08-24 10:28       ` Sylwester Nawrocki
2020-08-24 10:31         ` Krzysztof Kozlowski
2020-09-02  9:24           ` Sylwester Nawrocki
2020-09-15 12:43             ` Sylwester Nawrocki
2020-09-15 16:17               ` Stephen Boyd

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=159780681339.334488.10402512224012716827@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=krzk@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=lukasz.luba@arm.com \
    --cc=m.szyprowski@samsung.com \
    --cc=rong.a.chen@intel.com \
    --cc=snawrocki@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.