From: Jiri Kosina <jikos@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, Takashi Iwai <tiwai@suse.de>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: mm: uninterruptable tasks hanged on mmap_sem
Date: Tue, 2 Feb 2016 22:24:04 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1602022222060.22727@cbobk.fhfr.pm> (raw)
In-Reply-To: <CACT4Y+Z=qaJjzOFsksSHur-kED=Jf-JFk_M0jnMNq1y5RG278A@mail.gmail.com>
On Tue, 2 Feb 2016, Dmitry Vyukov wrote:
> Original log from fuzzer contained the following WARNING in
> mm/rmap.c:412. But when I tried to reproduce it, I hit these hanged
> processes instead. I can't reliably detect what program triggered
> what. So it may be related, or maybe a separate issue.
>
> ------------[ cut here ]------------
> kernel BUG at mm/rmap.c:412!
Are you by any chance in this test sending signals to the fuzzer?
If so, the bug I just fixed in floppy driver can cause all kinds of memory
corruptions in case you're running multithreaded accessess to /dev/fd0 and
sending singals to the threads that are trying to access /dev/fd0 at the
same time.
Could you please double check that the other floppy fix I've sent you a
couple days ago doesn't fix this as well? (this test makes sense only if
signals are involved though).
Thanks,
--
Jiri Kosina
SUSE Labs
--
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>
next prev parent reply other threads:[~2016-02-02 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 20:59 Dmitry Vyukov
2016-02-02 21:08 ` Jiri Kosina
2016-02-02 21:14 ` Dmitry Vyukov
2016-02-02 21:20 ` Dmitry Vyukov
2016-02-02 21:24 ` Jiri Kosina [this message]
2016-02-02 21:29 ` Dmitry Vyukov
2016-02-03 13:11 ` Jiri Kosina
2016-02-03 13:18 ` Dmitry Vyukov
2016-02-03 23:34 ` Jiri Kosina
2016-02-04 21:22 ` [PATCH] floppy: refactor open() flags handling (was Re: mm: uninterruptable tasks hanged on mmap_sem) Jiri Kosina
2016-02-05 13:43 ` Dmitry Vyukov
2016-02-05 13:51 ` [PATCH v2] " Jiri Kosina
2016-02-05 14:26 ` Dmitry Vyukov
2016-02-05 16:40 ` Jiri Kosina
2016-02-05 21:16 ` Dmitry Vyukov
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=alpine.LNX.2.00.1602022222060.22727@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=tiwai@suse.de \
/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