From: Dave Jones <davej@codemonkey.org.uk>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [4.7+] various memory corruption reports.
Date: Mon, 1 Aug 2016 12:37:31 -0400 [thread overview]
Message-ID: <20160801163731.xmlcb7vi2hfqe3ri@codemonkey.org.uk> (raw)
In-Reply-To: <579F2C73.6090406@gmail.com>
On Mon, Aug 01, 2016 at 02:03:15PM +0300, Andrey Ryabinin wrote:
> On 07/29/2016 09:39 PM, Dave Jones wrote:
> > On Fri, Jul 29, 2016 at 08:56:08PM +0300, Andrey Ryabinin wrote:
> >
> > > >> > I suspect this is false positives due to changes in KASAN.
> > > >> > Bisection probably will point to
> > > >> > 80a9201a5965f4715d5c09790862e0df84ce0614 ("mm, kasan: switch SLUB to
> > > >> > stackdepot, enable memory quarantine for SLUB)"
> > > >>
> > > >> good call. reverting that changeset seems to have solved it.
> > > > Could you please try with this?
> > > Actually, this is not quite right, it should be like this:
> >
> >
> > Seems to have stopped the corruption, but now I get NMi watchdog traces..
> >
>
> This should help:
Yep, this seems to have silenced all the problems I saw.
thanks,
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-08-01 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 15:05 Dave Jones
2016-07-29 15:19 ` Dave Jones
2016-07-29 15:21 ` Andrey Ryabinin
2016-07-29 15:49 ` Dave Jones
2016-07-29 17:32 ` Andrey Ryabinin
2016-07-29 17:56 ` Andrey Ryabinin
2016-07-29 18:39 ` Dave Jones
2016-08-01 11:03 ` Andrey Ryabinin
2016-08-01 16:37 ` Dave Jones [this message]
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=20160801163731.xmlcb7vi2hfqe3ri@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--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