From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f195.google.com ([209.85.215.195]:46378 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726213AbeIDMxS (ORCPT ); Tue, 4 Sep 2018 08:53:18 -0400 Received: by mail-pg1-f195.google.com with SMTP id b129-v6so1283864pga.13 for ; Tue, 04 Sep 2018 01:29:13 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <001a1148578c10e4700568e814eb@google.com> <20180404193504.GA7715@bombadil.infradead.org> <20180405032200.GC22358@thunk.org> <20180405032454.GD9301@bombadil.infradead.org> From: Dmitry Vyukov Date: Tue, 4 Sep 2018 10:28:52 +0200 Message-ID: Subject: Re: WARNING in up_write To: Matthew Wilcox Cc: "Theodore Y. Ts'o" , syzbot , linux-fsdevel , LKML , syzkaller-bugs , Al Viro Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Apr 5, 2018 at 10:22 AM, Dmitry Vyukov wrote: > On Thu, Apr 5, 2018 at 5:24 AM, Matthew Wilcox wrote: >> On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: >>> On Wed, Apr 04, 2018 at 12:35:04PM -0700, Matthew Wilcox wrote: >>> > On Wed, Apr 04, 2018 at 09:24:05PM +0200, Dmitry Vyukov wrote: >>> > > On Tue, Apr 3, 2018 at 4:01 AM, syzbot >>> > > wrote: >>> > > > DEBUG_LOCKS_WARN_ON(sem->owner != get_current()) >>> > > > WARNING: CPU: 1 PID: 4441 at kernel/locking/rwsem.c:133 up_write+0x1cc/0x210 >>> > > > kernel/locking/rwsem.c:133 >>> > > > Kernel panic - not syncing: panic_on_warn set ... >>> > >>> > Message-Id: <1522852646-2196-1-git-send-email-longman@redhat.com> >>> > >>> >>> We were way ahead of syzbot in this case. :-) >> >> Not really ... syzbot caught it Monday evening ;-) >> >> Date: Mon, 02 Apr 2018 19:01:01 -0700 >> From: syzbot >> To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, >> syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk >> Subject: WARNING in up_write > > :) > > #syz fix: locking/rwsem: Add up_write_non_owner() for percpu_up_write() The title was later changed to: #syz fix: locking/rwsem: Add a new RWSEM_ANONYMOUSLY_OWNED flag