Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1049552imm; Sat, 26 May 2018 19:36:36 -0700 (PDT) X-Google-Smtp-Source: AB8JxZov3qPFfEFN+UOOnjFwxeLFZZfK7gqPu+iz4npD8BSkRaDwt+ItA7cs4Kaf4DH1aD0LEKJl X-Received: by 2002:a17:902:54d:: with SMTP id 71-v6mr8432182plf.365.1527388596516; Sat, 26 May 2018 19:36:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527388596; cv=none; d=google.com; s=arc-20160816; b=K0RQwQQ9O/muCS477aEwbUZJdB7XWPJHsOGLwT33nlvqUFu/HnlawyI6kkpqpymfiS ESxeekvERqow2FAadjhaGU5wINIuaUXH4k0j+718p18hIsetGGVi/a4GIqMKez6Uu0eY DnW228p/4dQcjrpFWmHmw3REqNCUiFFBr8ZZbpMBPJJ64lnRi61JmtJrdNwV96pZqHI0 NTKHlQ9CSAgyhL0eijO+aIhwzppuKG2mTxPXXpJHVgUGOB938fIglJ3Dn3LNUxy63LRk oMse0gs6vab+mP2LcGSEzBNxWyjpXhSEZFkqbbseCKE2I1qcdktskdKpAaKvQ4xk0ovd 82Uw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=FSR8XtAWB14iPW1XLl+Yl8ZfbOwyHUOs0yXKuoiNFZY=; b=ZRNcXyks8H3711XxJrPdxm5+W8+XVx6bif9aFJcSLVfoPvt0A/vCDpW/0H9FAOvFzk Ltvwo323+Y4zNX31QOJZlGoAWYLnbHTacjU5vo435qdAd+ysKEBOlhACqEKB9XN3xwD4 QrnGJUWC+4RT7ejS0fD6qtVL07meIHDn10+0PhDwgJ0/M5CHTKhlmkNI+nLiTWxicgC2 c9AF3MxCWiUhnXlwVdcrxdQxLE5i8/iE7SGJ4SCLnrJEHMmjJbeA/E1jBlckWOKLQfTS JyaIpXVMFj57cA7aQW9yCWL+ojintsrdrpNO3+SNeaGAOBQXDoh2fcTyJGTdILjITCO/ jZ4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=FSODe/9A; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o4-v6si26174065plk.321.2018.05.26.19.36.19; Sat, 26 May 2018 19:36:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=FSODe/9A; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1032559AbeE0CgJ (ORCPT + 99 others); Sat, 26 May 2018 22:36:09 -0400 Received: from mail-yb0-f193.google.com ([209.85.213.193]:42608 "EHLO mail-yb0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1032500AbeE0CgH (ORCPT ); Sat, 26 May 2018 22:36:07 -0400 Received: by mail-yb0-f193.google.com with SMTP id d123-v6so3087968ybh.9; Sat, 26 May 2018 19:36:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=FSR8XtAWB14iPW1XLl+Yl8ZfbOwyHUOs0yXKuoiNFZY=; b=FSODe/9AVxX+FIMJrX98l1Nor7fBbu56ILqSWKgd4/V/CXVCS5pv/ZGAUA1ejr7Y1a Vv+kzphM703qxmqLIXm3+rBOBb45enyKeF2gAKAuRdBjET3wdCneZJDihLyOzlrDyHlK fJSuLsLn00fzSZdSwq5DX+cY+DuF2xvRggOeDX8KNobfXH7DjWcX2aWsTmV+ZY7CZVsT 6xzIzp0aE1sfLpFTYzhO0FmcPyeeIrsDtR0IxsIxHqIDzPM8si/TvJbVeyoGuVdWC6rJ H1eXP8pZOK6UJpP70AKea/Xo0SpUYG+DDdNBX1i9JAd16UOPDZE/BME8AKF73AwfY/fg Z6KQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=FSR8XtAWB14iPW1XLl+Yl8ZfbOwyHUOs0yXKuoiNFZY=; b=GvOujKcWVQyTh9X7V89wRDHu6y5JDjPV+zBNXYgrjgmOrwsJ9GEW19IuphX2A5Wb73 /ftqvodc29BAieAUuK+zvsLWfbQZl1yKXL7GUuZyFNEw6Tw9iMgceWxy4pGxLRaR/pD6 PGEvYXUgX8Od2odwYArI2xxCp1rCYET1737zDm8v0QZ2IdWbRt5kBMfRa7NRM0EVDXTm MdMSyKJQFcfI5efwHOlbeLJSc511vy13x8AWShncv5LcXEZsw8Br0XroAdwsGpcrNzu3 +ZnG6OCH08c+lVle7Ns8Ieam44t4TSnSlkrM6+4RbIERQshvFuut4iKBZerNTLrULM0S HPhA== X-Gm-Message-State: ALKqPwdeymhOsA2bIjt9ma/9Eo0nx5P7iglzbyM+glC6yijvq/hFNjWR gC2bDqpj+o1D1KaQqRHneMk= X-Received: by 2002:a25:dd87:: with SMTP id u129-v6mr4730377ybg.252.1527388566094; Sat, 26 May 2018 19:36:06 -0700 (PDT) Received: from localhost ([2620:10d:c091:180::1:f0c7]) by smtp.gmail.com with ESMTPSA id h5-v6sm3399270ywe.28.2018.05.26.19.36.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 26 May 2018 19:36:04 -0700 (PDT) Date: Sat, 26 May 2018 19:36:02 -0700 From: Tejun Heo To: Tetsuo Handa Cc: syzbot , syzkaller-bugs@googlegroups.com, jack@suse.cz, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk, axboe@kernel.dk, david@fromorbit.com, linux-block@vger.kernel.org Subject: Re: [PATCH] bdi: Fix another oops in wb_workfn() Message-ID: <20180527023602.GE1351649@devbig577.frc2.facebook.com> References: <000000000000cbd959056d1851ca@google.com> <0c7c5dea-7312-8a59-9d1b-5467f69719bf@I-love.SAKURA.ne.jp> <314ae2e0-c873-04ce-9cd5-fe2acadaee26@I-love.SAKURA.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <314ae2e0-c873-04ce-9cd5-fe2acadaee26@I-love.SAKURA.ne.jp> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, May 27, 2018 at 11:21:25AM +0900, Tetsuo Handa wrote: > From 8a8222698163d1fe180258566e9a3ff43f54fcd9 Mon Sep 17 00:00:00 2001 > From: Tetsuo Handa > Date: Sun, 27 May 2018 11:08:20 +0900 > Subject: [PATCH] bdi: Fix another oops in wb_workfn() > > syzbot is still hitting NULL pointer dereference at wb_workfn() [1]. > This might be because we overlooked that delayed_work_timer_fn() does not > check WB_registered before calling __queue_work() while mod_delayed_work() > does not wait for already started delayed_work_timer_fn() because it uses > del_timer() rather than del_timer_sync(). It shouldn't be that as dwork timer is an irq safe timer. Even if that's the case, the right thing to do would be fixing workqueue rather than reaching into workqueue internals from backing-dev code. Thanks. -- tejun