Received: by 10.213.65.68 with SMTP id h4csp3908632imn; Tue, 10 Apr 2018 06:32:07 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+MlNFT4m3BnQCAuAbzAvaL8Gddn/3jrkb6ZH83EjACn3hJr7aF7ftAwYWn3T9On4gGpZwu X-Received: by 10.98.13.23 with SMTP id v23mr388068pfi.202.1523367127344; Tue, 10 Apr 2018 06:32:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523367127; cv=none; d=google.com; s=arc-20160816; b=hL7p5YUujRINsLXIVxtKRrSFh1Pn0m2yQNBzRJLrxfS9NHhPF2G3KfQhLZJl2nE3sc U5UQ/7VMW00ptm7MCgXOD96OvodESl6YdyE05eLLQnt3SQvkwnVNWuEA08gTSEavHfdU AO93NSTatJ9DqczG/LypbNig2hXY4DMVOsUHEaadBgNrzZT2eAUpQ8vPXb6FNtPiRzr9 LLrlJa7isDIxhYEoqroSQgM3/dX/kOEw605J4Zgc8YHnQt1HDedsinwlDLXpjdWc/kHb SZAehZioUJ42V4bnOWrdUjDDXfMNMqLiAf54C5NEoSYSVuOBduws3K1tgnQFc3npLeaV tckQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=urIjVoklUH2WTZ4ISIxIBjK5hUsDn4m3cwqOS7rMDUU=; b=xLwLCftWCU/fsW9ecKTEm3R9cUEkI1IlOB821XvgdVU43CqppAryZTvbMHAqGpXJT7 vR4Ug3KKUngADhumPC79NXvmhOtqn/vpnYb3Ispc8daU5rJhgWkhNkdCJqgy0maXpBBQ 2mHurDkfoCNcvWnbuA/hb258WnBxcYh3jzeB7+9cjBgi4dOxF6MrTlnKSlA85w7ylOFg J0z8KF4TjVh7bDvfgdEU5idAmZaFZTafR3vO5/1Xnea4qGAZdssKF2VTuj06c7ZyRiy5 ER6z3P/lfpi9E2993ffmSC7/6nSgEqIlPg6eFLms3XBcwG+jtrM2++APe3ZvMClYESRX ZZ5g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=GBKEbdlN; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a87si2089455pfe.399.2018.04.10.06.31.30; Tue, 10 Apr 2018 06:32:07 -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=pass header.i=@google.com header.s=20161025 header.b=GBKEbdlN; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753960AbeDJNZL (ORCPT + 99 others); Tue, 10 Apr 2018 09:25:11 -0400 Received: from mail-pf0-f171.google.com ([209.85.192.171]:37187 "EHLO mail-pf0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753713AbeDJNZH (ORCPT ); Tue, 10 Apr 2018 09:25:07 -0400 Received: by mail-pf0-f171.google.com with SMTP id p6so4736886pfn.4 for ; Tue, 10 Apr 2018 06:25:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=urIjVoklUH2WTZ4ISIxIBjK5hUsDn4m3cwqOS7rMDUU=; b=GBKEbdlNcVAuvPjCAaZrDDpZL78fFnO2wCZHTq2x6ifAVjO47RoWSaD3T6LN6ZPgEC WfbMw+YZU1QiIZMA9GzQvUUHXawVB5On/DW8THNBgXXTXwPQJ1+ZZ9Oa1bWx/84i3uCo sBT4p4BtNb/WHWAXZOuiOdVVAjt6FYBQ9KbXoO0R2gYvVxEKPkm6B7GM3MPIinRvLU1f lXI7RSic+cP2vXs9v6hKGjWiv+Zl/S0rcap2TPrXWtrHfCBtBFM6ssuun8k+mxrwrqrU xvSFeXK1ZSmcph1AYj+jJ567xa/f+t2R9KIUpVH7+8hPGAytQKYaVZq8sgU41DZmRKio ly8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=urIjVoklUH2WTZ4ISIxIBjK5hUsDn4m3cwqOS7rMDUU=; b=GWsRA6CwK36umyKc8rv4o5KPW/p1dC7r4xgYeOdslyc+8B5tqvvj/QohATUsFmh8p7 QT7UGKPocHWrd2fSQaoZ6A5pGuAZFHCH5D+5E1G33r4wHrBkitYGd51K/9wP95NJkHUZ naDt+GQ6wDseqbVBKQVJHPApzo0CxPn33iAdqquacjL3INHrWyMfwjGOBbk/U/cyZQz1 wSaVUli9K8KI0uv0UIPec7+xda9St+8FtofHWyM3NIY7LglO0gPoDrpHZcp29GbiOvY/ y8wI1q3iiQ3dg0uspckLnDZBTErSdDOhut5yziksMePY8ORSZE1Qekd2YFGaz8viBre5 vQtg== X-Gm-Message-State: ALQs6tBjY0inhJuVRMfiLe7tw43EibE6KtlmDMaBap4d6HCdHYKcRVrh Z7mm3iEdFH3OvZF3bin2hRsVORWTrYhoaP/fv61TPA== X-Received: by 10.98.236.86 with SMTP id k83mr378486pfh.84.1523366706521; Tue, 10 Apr 2018 06:25:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.182.136 with HTTP; Tue, 10 Apr 2018 06:24:46 -0700 (PDT) In-Reply-To: <201804102204.BDF48937.LMHJVFOFFOOSQt@I-love.SAKURA.ne.jp> References: <652eab47-81b5-3249-3c78-427eeec45fbc@I-love.SAKURA.ne.jp> <2e093801-6d71-6747-42df-52f191811ad0@I-love.SAKURA.ne.jp> <87bdec75-3c59-6587-2436-1470263ab11f@kernel.dk> <59a08949-7e2f-42ff-edda-f24a6c624551@I-love.SAKURA.ne.jp> <201804102204.BDF48937.LMHJVFOFFOOSQt@I-love.SAKURA.ne.jp> From: Dmitry Vyukov Date: Tue, 10 Apr 2018 15:24:46 +0200 Message-ID: Subject: Re: INFO: task hung in __blkdev_get To: Tetsuo Handa Cc: Jens Axboe , Ming Lei , Ingo Molnar , Peter Zijlstra , syzbot , LKML , syzkaller-bugs , Omar Sandoval Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 10, 2018 at 3:04 PM, Tetsuo Handa wrote: > Dmitry Vyukov wrote: >> On Tue, Apr 10, 2018 at 12:55 PM, Tetsuo Handa >> wrote: >> > Hello. >> > >> > Since syzbot is reporting so many hung up bug which involves /dev/loopX , >> > is it possible to "temporarily" apply below patch for testing under syzbot >> >> Unfortunately it's not possible, for full explanation please see: >> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#no-custom-patches >> > > I mean, sending custom patch to linux.git for -rc and revert the custom patch > before -final is released. It won't take so much period until we get the result. Ah, I see, then I guess it wasn't a question to me. > If syzbot can test arbitrary git tree instead of linux.git, making a branch > which contains custom patches would be possible. syzbot tests a set of trees (also net-next and bpf-next at the moment). But see this reply to Takashi re a similar request: https://groups.google.com/forum/#!msg/syzkaller-bugs/7ucgCkAJKSk/skZjgavRAQAJ Note that a syzkaller instances will produce several hundreds of different crashes within a day, and then a big question is what to do with them. What's perfectly possible though is running syzkaller locally, and you can do it on just any tree you want. I've recently put a script that setups syzkaller end-to-end with config, compiler and image that syzbot uses: https://github.com/google/syzkaller/blob/master/tools/demo_setup.sh (that uses v4.13, but you can change this to any kernel version).