From: Borislav Petkov <bp@suse.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKP <lkp@01.org>, lkml <linux-kernel@vger.kernel.org>,
Ye Xiaolong <xiaolong.ye@intel.com>
Subject: Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
Date: Sun, 19 Feb 2017 01:10:47 +0100 [thread overview]
Message-ID: <20170219001047.ivdkkkmrml6bh5v3@pd.tnic> (raw)
In-Reply-To: <20170218232950.picqhk2xlmx3uh4l@wfg-t540p.sh.intel.com>
Hey Fengguang,
On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote:
> Good point! I noticed it too while sending out the report. It'll be
> showed as this in future:
>
> https://github.com/0day-ci/linux/commits/Borislav-Petkov/x86-Optimize-clear_page/20170210-053052
How about pointing to the patch directly?
https://github.com/0day-ci/linux/commit/0ad07c8104eb5c12dfcb86581c1cc657183496cc
> Sorry the 2nd report was send out manually and I only checked the
> emails in my _current_ mbox. Since the previous report email has been
> archived, it slipped through the duplication check.
No worries - this was all a prelude to me hinting at the email-based
talking to the bot :-)
> CC Xiaolong. It's possible to automate the test-of-fixup-patches.
> Firstly find out the original email report by the Message-ID being
> replied to. Then fetch all the information required for deciding where
> the patch should be applied to, parameters to auto-testing the patch.
Sounds like a plan.
It would probably even be easier for the bot if the reply-mail contained
specially-formatted hints like:
TEST-WITH-BELOW-PATCH: ...
or so.
Btw, another nice aspect of this talking back to the bot is that before
I, as a recipient of the bug report, go and try to prepare a guest or
find a machine to reproduce properly, I can send a quick diff to the bot
in the meantime and say, "try this on the guest. I have a hunch it might
fix it."
> Yeah we have a TODO to do email based on-demand service, which looks
> close to your proposal.
Cool. Ping me if you need testers.
Thanks!
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2017-02-19 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170218050153.wc7zhrtv5q5wjszq@wfg-t540p.sh.intel.com>
2017-02-18 14:48 ` [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Borislav Petkov
2017-02-18 23:29 ` Fengguang Wu
2017-02-19 0:10 ` Borislav Petkov [this message]
2017-02-19 1:06 ` Fengguang Wu
2017-02-19 13:50 ` Borislav Petkov
2017-02-20 3:03 ` Fengguang Wu
2017-02-20 9:35 ` Borislav Petkov
2017-02-21 0:00 ` email/patch test requests to 0day robot Fengguang Wu
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=20170219001047.ivdkkkmrml6bh5v3@pd.tnic \
--to=bp@suse.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=xiaolong.ye@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