linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yuri Norov <ynorov@marvell.com>
To: Qian Cai <cai@lca.pw>
Cc: Andrey Konovalov <andreyknvl@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [EXT] "lib: rework bitmap_parse()" triggers invalid access errors
Date: Thu, 30 May 2019 23:20:45 +0000	[thread overview]
Message-ID: <BN6PR1801MB20652E92AA9F04B2490BD4F3CB180@BN6PR1801MB2065.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1559242868.6132.35.camel@lca.pw>

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

From: Qian Cai <cai@lca.pw>
Sent: Thursday, May 30, 2019 11:01 PM
To: Yuri Norov
Cc: Andrey Konovalov; linux-kernel@vger.kernel.org; Andy Shevchenko; Andrew Morton; linux-mm@kvack.org
Subject: "lib: rework bitmap_parse()" triggers invalid access errors

> The linux-next commit "lib: rework bitmap_parse" triggers errors below during
> boot on both arm64 and powerpc with KASAN_SW_TAGS or SLUB_DEBUG enabled.

> Reverted the commit and its dependency (lib: opencode in_str()) fixed the issue.

Thanks, I'll take a look

[...]


[-- Attachment #2: Type: text/html, Size: 1684 bytes --]

  reply	other threads:[~2019-05-31  0:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 19:01 Qian Cai
2019-05-30 23:20 ` Yuri Norov [this message]
2019-06-04 18:23 ` Qian Cai
2019-06-05  8:01   ` [EXT] " Yuri Norov
2019-06-06 16:09     ` Qian Cai
2019-06-07  1:57       ` Yury Norov

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=BN6PR1801MB20652E92AA9F04B2490BD4F3CB180@BN6PR1801MB2065.namprd18.prod.outlook.com \
    --to=ynorov@marvell.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=cai@lca.pw \
    --cc=linux-kernel@vger.kernel.org \
    --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