[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190321172833.GB12297@redhat.com>
Date: Thu, 21 Mar 2019 18:28:33 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: syzbot <syzbot+b70f2aabc707c69c9239@...kaller.appspotmail.com>,
chanho.min@....com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, pavel@....cz,
rafael.j.wysocki@...el.com, syzkaller-bugs@...glegroups.com,
viro@...iv.linux.org.uk, Ingo Molnar <mingo@...e.hu>
Subject: Re: WARNING: syz-executor still has locks held!
On 03/20, Michal Hocko wrote:
>
> So we need
> freezable_schedule_unsafe unsafe here to workaround the original problem
> and do not trigger the warning.
Yes, but note the comment above freezable_schedule_unsafe() ;)
that is why I didn't even try to suggest to use _unsafe() instead of reverting.
And to remind, until we solve the problem with cred_guard_mutex the freezer
can fail anyway although much less likely.
Oleg.
Powered by blists - more mailing lists