[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180210013640.GN30522@ZenIV.linux.org.uk>
Date: Sat, 10 Feb 2018 01:36:40 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Eric Biggers <ebiggers3@...il.com>,
syzbot <syzbot+bacbe5d8791f30c9cee5@...kaller.appspotmail.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
Dan Williams <dan.j.williams@...el.com>,
James Morse <james.morse@....com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>, Ingo Molnar <mingo@...nel.org>,
syzkaller-bugs@...glegroups.com
Subject: Re: possible deadlock in get_user_pages_unlocked
On Fri, Feb 02, 2018 at 09:57:27AM +0100, Dmitry Vyukov wrote:
> syzbot tests for up to 5 minutes. However, if there is a race involved
> then you may need more time because the crash is probabilistic.
> But from what I see most of the time, if one can't reproduce it
> easily, it's usually due to some differences in setup that just don't
> allow the crash to happen at all.
> FWIW syzbot re-runs each reproducer on a freshly booted dedicated VM
> and what it provided is the kernel output it got during run of the
> provided program. So we have reasonably high assurance that this
> reproducer worked in at least one setup.
Could you guys check if the following fixes the reproducer?
diff --git a/mm/gup.c b/mm/gup.c
index 61015793f952..058a9a8e4e2e 100644
--- a/mm/gup.c
+++ b/mm/gup.c
@@ -861,6 +861,9 @@ static __always_inline long __get_user_pages_locked(struct task_struct *tsk,
BUG_ON(*locked != 1);
}
+ if (flags & FOLL_NOWAIT)
+ locked = NULL;
+
if (pages)
flags |= FOLL_GET;
Powered by blists - more mailing lists