From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by kanga.kvack.org (Postfix) with ESMTP id F33C26B0005 for ; Tue, 2 Feb 2016 16:30:07 -0500 (EST) Received: by mail-wm0-f46.google.com with SMTP id l66so42626028wml.0 for ; Tue, 02 Feb 2016 13:30:07 -0800 (PST) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com. [2a00:1450:400c:c09::22f]) by mx.google.com with ESMTPS id u8si4882618wje.114.2016.02.02.13.30.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Feb 2016 13:30:06 -0800 (PST) Received: by mail-wm0-x22f.google.com with SMTP id p63so137734252wmp.1 for ; Tue, 02 Feb 2016 13:30:06 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Dmitry Vyukov Date: Tue, 2 Feb 2016 22:29:46 +0100 Message-ID: Subject: Re: mm: uninterruptable tasks hanged on mmap_sem Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: Jiri Kosina Cc: Andrew Morton , "Kirill A. Shutemov" , Oleg Nesterov , Konstantin Khlebnikov , "linux-mm@kvack.org" , LKML , Takashi Iwai , syzkaller , Kostya Serebryany , Alexander Potapenko , Sasha Levin On Tue, Feb 2, 2016 at 10:24 PM, Jiri Kosina wrote: > 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). I have "floppy: fix lock_fdc() signal handling" applied (the final, second version). The process is multithreaded and it can well receive SIGKILLs. -- 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: email@kvack.org