All of lore.kernel.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: Intermittent memory corruption with v4.13-rc6+ and earlier
Date: Thu, 24 Aug 2017 13:36:48 +0100	[thread overview]
Message-ID: <20170824123647.GA19698@leverpostej> (raw)
In-Reply-To: <20170824114833.GH5943@dhcp22.suse.cz>

On Thu, Aug 24, 2017 at 01:48:34PM +0200, Michal Hocko wrote:
> On Thu 24-08-17 12:37:43, Mark Rutland wrote:
> > Hi,
> > 
> > I'm chasing intermittent memory corruption bugs seen at least on rc5,
> > rc6, and yesterday's HEAD (98b9f8a4549909c6), on arm64. 
> > 
> > It looks like we make use of dangling references to a freed struct file,
> > which is caught by KASAN. Without KASAN, I see a number of other
> > intermittent issues that I suspect are the result of this memory
> > corruption. I've included an example splat below, complete with KASAN's
> > alloc/free traces at the end of this mail.
> 
> Is it possible this is the same issue as the one fixed by
> http://lkml.kernel.org/r/20170823211408.31198-1-ebiggers3 at gmail.com?

That sounds plausible, and so far the fix seems to help. Thanks for the
pointer!

I'll leave that running for a while, just in case.

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jan Kara <jack@suse.cz>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vlastimil Babka <vbabka@suse.cz>,
	will.deacon@arm.com
Subject: Re: Intermittent memory corruption with v4.13-rc6+ and earlier
Date: Thu, 24 Aug 2017 13:36:48 +0100	[thread overview]
Message-ID: <20170824123647.GA19698@leverpostej> (raw)
In-Reply-To: <20170824114833.GH5943@dhcp22.suse.cz>

On Thu, Aug 24, 2017 at 01:48:34PM +0200, Michal Hocko wrote:
> On Thu 24-08-17 12:37:43, Mark Rutland wrote:
> > Hi,
> > 
> > I'm chasing intermittent memory corruption bugs seen at least on rc5,
> > rc6, and yesterday's HEAD (98b9f8a4549909c6), on arm64. 
> > 
> > It looks like we make use of dangling references to a freed struct file,
> > which is caught by KASAN. Without KASAN, I see a number of other
> > intermittent issues that I suspect are the result of this memory
> > corruption. I've included an example splat below, complete with KASAN's
> > alloc/free traces at the end of this mail.
> 
> Is it possible this is the same issue as the one fixed by
> http://lkml.kernel.org/r/20170823211408.31198-1-ebiggers3@gmail.com?

That sounds plausible, and so far the fix seems to help. Thanks for the
pointer!

I'll leave that running for a while, just in case.

Thanks,
Mark.

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jan Kara <jack@suse.cz>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vlastimil Babka <vbabka@suse.cz>,
	will.deacon@arm.com
Subject: Re: Intermittent memory corruption with v4.13-rc6+ and earlier
Date: Thu, 24 Aug 2017 13:36:48 +0100	[thread overview]
Message-ID: <20170824123647.GA19698@leverpostej> (raw)
In-Reply-To: <20170824114833.GH5943@dhcp22.suse.cz>

On Thu, Aug 24, 2017 at 01:48:34PM +0200, Michal Hocko wrote:
> On Thu 24-08-17 12:37:43, Mark Rutland wrote:
> > Hi,
> > 
> > I'm chasing intermittent memory corruption bugs seen at least on rc5,
> > rc6, and yesterday's HEAD (98b9f8a4549909c6), on arm64. 
> > 
> > It looks like we make use of dangling references to a freed struct file,
> > which is caught by KASAN. Without KASAN, I see a number of other
> > intermittent issues that I suspect are the result of this memory
> > corruption. I've included an example splat below, complete with KASAN's
> > alloc/free traces at the end of this mail.
> 
> Is it possible this is the same issue as the one fixed by
> http://lkml.kernel.org/r/20170823211408.31198-1-ebiggers3@gmail.com?

That sounds plausible, and so far the fix seems to help. Thanks for the
pointer!

I'll leave that running for a while, just in case.

Thanks,
Mark.

  reply	other threads:[~2017-08-24 12:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 11:37 Intermittent memory corruption with v4.13-rc6+ and earlier Mark Rutland
2017-08-24 11:37 ` Mark Rutland
2017-08-24 11:37 ` Mark Rutland
2017-08-24 11:48 ` Michal Hocko
2017-08-24 11:48   ` Michal Hocko
2017-08-24 11:48   ` Michal Hocko
2017-08-24 12:36   ` Mark Rutland [this message]
2017-08-24 12:36     ` Mark Rutland
2017-08-24 12:36     ` Mark Rutland
2017-08-24 12:59     ` Michal Hocko
2017-08-24 12:59       ` Michal Hocko
2017-08-24 12:59       ` Michal Hocko

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=20170824123647.GA19698@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.