From: balducci@units.it
To: mgorman@techsingularity.net
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: Re: [Bug 203715] BUG: unable to handle kernel NULL pointer dereference under stress (possibly related to https://lkml.org/lkml/2019/5/24/292 ?)
Date: Tue, 25 Jun 2019 08:08:10 +0200 [thread overview]
Message-ID: <32196.1561442914@dschgrazlin2.units.it> (raw)
In-Reply-To: Your message of "Mon, 24 Jun 2019 14:19:32 -0000." <bug-203715-9581-IIXSanmjPc@https.bugzilla.kernel.org/>
> I was under the impression that this bug was potentially solved. From openSUS
> E,
> I know that a similar class of bug was fixed by at least 5.1.9 and comment 23
> indicates that for one user at least, this bug has disappeared. Can you confi
> rm
> whether the latest 5.1 -stable kernel is ok for you or are you still seeing
> problems? If so, can you repost the latest oops on a recent kernel so I can t
> ry
> determine if it's a similar or different bug. Thanks.
just tried a firefox build with 5.1.14 and didn't experience any problem
However, I wouldn't close this before I can successfully complete some
more tests, which I plan to do immediately
I'll report both in case I'll find problems again and also if everything
goes well (so that the issue can be closed with reasonable confidence)
thanks a lot
ciao
-g
next parent reply other threads:[~2019-06-25 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-203715-9581-IIXSanmjPc@https.bugzilla.kernel.org/>
2019-06-25 6:08 ` balducci [this message]
[not found] <bug-203715-9581-Ws6dSkF6YF@https.bugzilla.kernel.org/>
2019-06-28 6:16 ` balducci
[not found] <bug-203715-9581-JKJKlU0qlh@https.bugzilla.kernel.org/>
2019-06-07 6:22 ` balducci
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=32196.1561442914@dschgrazlin2.units.it \
--to=balducci@units.it \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
/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