From: Vlastimil Babka <vbabka@suse.cz>
To: "Leonardo Soares Müller" <leozinho29_eu@hotmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Colascione <dancol@google.com>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [Bug 201377] New: Kernel BUG under memory pressure: unable to handle kernel NULL pointer dereference at 00000000000000f0
Date: Sun, 14 Oct 2018 22:14:57 +0200 [thread overview]
Message-ID: <863182da-4302-07a5-7280-0c017561b7eb@suse.cz> (raw)
In-Reply-To: <RO1P152MB14838EBA2F5ACD64A1CD3C3697FC0@RO1P152MB1483.LAMP152.PROD.OUTLOOK.COM>
On 10/14/18 8:07 PM, Leonardo Soares MA 1/4 ller wrote:
> This patch applied on 4.19-rc7 corrected the problem to me and the
> script is no longer triggering the kernel bug.
Great! Can we add your Tested-by: then?
> I completely skipped 4.18 because there were multiple regressions
> affecting my computer. 4.19-rc6 and 4.19-rc7 have most regressions fixed
> but then this issue appeared.
>
> The first kernel version released I found with this problem is 4.18-rc4,
OK, that confirms the smaps_rollup problem is indeed older than my
rewrite. Unless it's a typo and you mean 4.19-rc4 since you "skipped 4.18".
> but bisecting between 4.18-rc3 and 4.18-rc4 failed: on boot there was
> one message starting with [UNSUPP] and with something about "Arbitrary
> File System".
>
next prev parent reply other threads:[~2018-10-14 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201377-27@https.bugzilla.kernel.org/>
[not found] ` <20181012155533.2f15a8bb35103aa1fa87962e@linux-foundation.org>
2018-10-12 22:56 ` Andrew Morton
2018-10-13 12:57 ` Vlastimil Babka
2018-10-14 7:17 ` Vlastimil Babka
2018-10-14 18:07 ` Leonardo Soares Müller
2018-10-14 20:14 ` Vlastimil Babka [this message]
2018-10-14 22:07 ` Leonardo Soares Müller
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=863182da-4302-07a5-7280-0c017561b7eb@suse.cz \
--to=vbabka@suse.cz \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dancol@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=leozinho29_eu@hotmail.com \
--cc=linux-mm@kvack.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