Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1584044
| From | Borislav Petkov <bp@suse.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 |
| Date | 2017-02-19 01:20 +0100 |
| Message-ID | <tcnol-kh-3@gated-at.bofh.it> (permalink) |
| References | <tcf7s-3zv-11@gated-at.bofh.it> <tcf7s-3zv-9@gated-at.bofh.it> <tcmLF-8jc-65@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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)
--
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Borislav Petkov <bp@suse.de> - 2017-02-18 16:30 +0100
Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Fengguang Wu <fengguang.wu@intel.com> - 2017-02-19 00:40 +0100
Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Borislav Petkov <bp@suse.de> - 2017-02-19 01:20 +0100
Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Fengguang Wu <fengguang.wu@intel.com> - 2017-02-19 02:10 +0100
Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Borislav Petkov <bp@suse.de> - 2017-02-19 15:00 +0100
Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Fengguang Wu <fengguang.wu@intel.com> - 2017-02-20 04:10 +0100
Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Borislav Petkov <bp@suse.de> - 2017-02-20 11:20 +0100
email/patch test requests to 0day robot Fengguang Wu <fengguang.wu@intel.com> - 2017-02-21 01:10 +0100
csiph-web