linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Igor Stoppa <igor.stoppa@huawei.com>
To: mhocko@kernel.org
Cc: willy@infradead.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Igor Stoppa <igor.stoppa@huawei.com>
Subject: [Question PATCH 0/1] mm: crash in vmalloc_to_page - misuse or bug?
Date: Thu, 22 Feb 2018 16:13:23 +0200	[thread overview]
Message-ID: <20180222141324.5696-1-igor.stoppa@huawei.com> (raw)

While trying to change the code of find_vm_area, I got an automated
notification that my code was breaking the testing of i386, based on the
0-day testing automation from 01.org

I started investigating the issue and noticed that it seems to be
reproducible also on top of plain 4.16-rc2, without any of my patches.

I'm still not 100% sure that I'm doing something sane, but I thought it
might be good to share the finding.

The patch contains both a minimal change, to trigger the crash, and a
snippet of the log of the crash i get.

Igor Stoppa (1):
  crash vmalloc_to_page()

 mm/vmalloc.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

-- 
2.14.1

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

             reply	other threads:[~2018-02-22 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 14:13 Igor Stoppa [this message]
2018-02-22 14:13 ` [PATCH 1/1] crash vmalloc_to_page() Igor Stoppa
2018-03-02 12:16   ` f7f99cf8bd: kernel test robot
2018-03-02 13:23 ` [Question PATCH 0/1] mm: crash in vmalloc_to_page - misuse or bug? Igor Stoppa

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=20180222141324.5696-1-igor.stoppa@huawei.com \
    --to=igor.stoppa@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox