From: 'Christoph Moench-Tegeder' <cmt@burggraben.net>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: 'Michael Collins' <mike@ark-net.org>,
'Juergen Gross' <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
'Alex Braunegg' <alex.braunegg@gmail.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [BUG] kernel bug encountered at drivers/net/xen-netback/netback.c:430!
Date: Sun, 7 Jan 2018 23:19:05 +0100 [thread overview]
Message-ID: <20180107221904.GA78680@elch.exwg.net> (raw)
In-Reply-To: <3104994914c94a26baed6195f486c03f@AMSPEX02CL03.citrite.net>
## Paul Durrant (Paul.Durrant@citrix.com):
> > I could try a new kernel (KPTI, yay!) with that "mildly suspicious" commit
> > cc8737a5fe9051b7fa052b08c57ddb9f539c389a reverted on the weekend and
> > report back (just to rule that out - like you, I don't really believe
> > that this is the cause).
> > For the record, I'm still running 4.13.16 on the Dom0 (that's the last
> > working Dom0 kernel).
>
> Thanks. Well, that's the only netback commit that's in master but not in
> 4.13.16 so it would be useful to conclusively rule that out as a cause.
Funny thing: with that commit reverted, I'm running 4.14.12 on my Dom0.
That's holding much longer than any 4.4 kernel on that host before.
That's interesing, as the crashing code looks more correct (at least
for me and some compiler...), and the change is rather small.
Regards,
Christoph
--
Spare Space
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-01-07 22:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 6:40 [BUG] kernel bug encountered at drivers/net/xen-netback/netback.c:430! Alex Braunegg
2017-12-22 6:47 ` Juergen Gross
2017-12-22 20:35 ` Alex Braunegg
2017-12-28 18:05 ` Michael Collins
2017-12-28 19:31 ` Alex Braunegg
2018-01-03 13:54 ` Paul Durrant
2018-01-03 18:43 ` Alex Braunegg
2018-01-03 20:33 ` Christoph Moench-Tegeder
2018-01-04 10:29 ` Paul Durrant
2018-01-07 22:19 ` 'Christoph Moench-Tegeder' [this message]
2018-01-08 9:35 ` Paul Durrant
2018-01-09 9:44 ` Paul Durrant
2018-01-10 12:52 ` Paul Durrant
2018-01-10 13:58 ` Paul Durrant
2018-01-10 17:53 ` 'Christoph Moench-Tegeder'
2018-01-10 19:55 ` Alex Braunegg
-- strict thread matches above, loose matches on Subject: below --
2017-12-20 21:03 Alex Braunegg
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=20180107221904.GA78680@elch.exwg.net \
--to=cmt@burggraben.net \
--cc=Paul.Durrant@citrix.com \
--cc=alex.braunegg@gmail.com \
--cc=jgross@suse.com \
--cc=mike@ark-net.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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).