From: Sebastian Ott <sebott@linux.vnet.ibm.com>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Uecker <Martin.Uecker@med.uni-goettingen.de>,
Ingo Molnar <mingo@kernel.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Subject: Re: [bisected] 3c8ba0d61d04ced9f8d9ff93977995a9e4e96e91 oopses on s390
Date: Fri, 6 Apr 2018 20:10:57 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.21.1804062009040.1819@schleppi> (raw)
In-Reply-To: <CAGXu5jKLsdfHEySg1w5EKO3Tt3=nWh7txWVsU6V65i3vS=Z2xw@mail.gmail.com>
On Fri, 6 Apr 2018, Kees Cook wrote:
> On Fri, Apr 6, 2018 at 9:47 AM, Kees Cook <keescook@chromium.org> wrote:
> > On Fri, Apr 6, 2018 at 2:47 AM, Sebastian Ott <sebott@linux.vnet.ibm.com> wrote:
> >> Today's kernel oopsed on s390. Bisect points to:
> >> 3c8ba0d61d04 ("kernel.h: Retain constant expression output for max()/min()")
> >>
> >> [ 1.898277] dasd-eckd 0.0.3304: DASD with 4 KB/block, 21636720 KB total size, 48 KB/track, compatible disk layout
> >> [ 1.898308] ------------[ cut here ]------------
> >> [ 1.898310] kernel BUG at block/bio.c:1798!
> >
> > Well that's extremely bad. :(
> >
> >> Bisect log and config attached. I'll look at min/max users in the affected
> >> areas later today.
> >
> > Seems like a comparison of objdump output with/without the patch may
> > be needed. And why is this s390 only? Ugh.
>
> I did a objdump diff with your .config and it's rather large -- mostly
> seems to be register swaps, so it's not easy to browse.
Yes, I'm looking at that too.
> BTW, what version of gcc did you use? I built using:
gcc version 7.2.0 (GCC)
next prev parent reply other threads:[~2018-04-06 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 9:47 [bisected] 3c8ba0d61d04ced9f8d9ff93977995a9e4e96e91 oopses on s390 Sebastian Ott
2018-04-06 16:47 ` Kees Cook
2018-04-06 18:02 ` Kees Cook
2018-04-06 18:10 ` Sebastian Ott [this message]
2018-04-09 16:18 ` Sebastian Ott
2018-04-09 17:00 ` Sebastian Ott
2018-04-09 17:03 ` Linus Torvalds
2018-04-09 17:11 ` Sebastian Ott
2018-04-09 17:15 ` Linus Torvalds
2018-04-09 17:14 ` Linus Torvalds
2018-04-09 17:27 ` Sebastian Ott
2018-04-09 17:32 ` Linus Torvalds
2018-04-09 18:00 ` Kees Cook
2018-04-09 18:17 ` Linus Torvalds
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=alpine.LFD.2.21.1804062009040.1819@schleppi \
--to=sebott@linux.vnet.ibm.com \
--cc=Martin.Uecker@med.uni-goettingen.de \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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