Received: by 10.192.165.156 with SMTP id m28csp206120imm; Thu, 12 Apr 2018 20:10:25 -0700 (PDT) X-Google-Smtp-Source: AIpwx495c7hQ+uGtqf/w7CueB5kDjZDAuis6CM3jdFg06CIn+3ZIq07GHrJZ6Jd4IWzu5/ZutxgZ X-Received: by 10.101.102.12 with SMTP id w12mr2698789pgv.419.1523589024946; Thu, 12 Apr 2018 20:10:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523589024; cv=none; d=google.com; s=arc-20160816; b=u9w/AyESq9BtNRryYEZMLeBk0ZJgIXkDx6VxZnmEsSz4s8ivyMTV4xW15vSVUpy/XN 0p8WTvjvbuHdy0QyimYyk7r7ZJDWvlynLYqO5bTmAOO2s1fsxxyIOaUNYoTC3K1joxxg Tv6veD6s2tp47aRQ0N6jOWrtBdmcBoJmkKLaLjyfCBc8hkxYG9WEymFkV8hkCUTdnWkV YstqGCD692mJOMJ95X+hpuLnX9o1JSsZH7iDlPgGvKRDpqm88vkL38So/nu3Zk1XbGsy xAiTkqEkpyXFZk6PZbWFHwszDUGsPfntcgbLQ6hqgWPOzD1btaG2Nrn6gbEWF+bPbqlT vanA== 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:dkim-signature :arc-authentication-results; bh=jmBJyRO2T5yHV98lFnJReDtxz4k59RvLFqn3fwWDkhA=; b=BlImzhC04vdAZILWco1q6062tJl+FSPcNXGMuIrlBl2gWFR5eDZzuqaDG5WTFBvtzb 9KXsFQ57+6r/ZGvSl+fI3N/1RNE2tiuxqQdL8wg1cf+GPeGOzH1sZNNU1Dbwd63iZ1Py 2pxtPD77G9by6OsQZ+6TJelpc0cP0yigAHMIwc54bhwVbdr9xSWJVZ8pIyolk6m5KJJ8 CR2O7fl79l3DGZMyGdB6Es1MMtJvEPVA2fyBTDCh7pjYs//GcO87z8h2Nr8dVHoqWYju EGvVmzMt7vLpOsQlqr+tAxEtxmmqW8fUQLBLJIE8WtpelnHj+wNNYm2JdUFXA4qZMJJw MMvw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@google.com header.s=20161025 header.b=qvgFijGT; dkim=fail header.i=@chromium.org header.s=google header.b=jjcmdOP9; 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=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d17si3238094pgv.576.2018.04.12.20.10.10; Thu, 12 Apr 2018 20:10:24 -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=@google.com header.s=20161025 header.b=qvgFijGT; dkim=fail header.i=@chromium.org header.s=google header.b=jjcmdOP9; 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=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752996AbeDMDCr (ORCPT + 99 others); Thu, 12 Apr 2018 23:02:47 -0400 Received: from mail-vk0-f54.google.com ([209.85.213.54]:46427 "EHLO mail-vk0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752077AbeDMDCp (ORCPT ); Thu, 12 Apr 2018 23:02:45 -0400 Received: by mail-vk0-f54.google.com with SMTP id v205so4532252vkv.13 for ; Thu, 12 Apr 2018 20:02:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jmBJyRO2T5yHV98lFnJReDtxz4k59RvLFqn3fwWDkhA=; b=qvgFijGTyn0mUKuzRnjkkCvcjMyAmLs+WSJwfXyv2SDBf78NnBXWGxLC2CJnqEVnvi MMvAKIaX5S1ZHq27L4CHmmf/3Bfn6hyT52Sb8VTeaUJ4ZQf9yxCWWGYxFYj4yZ1lJah9 cgbkg2phbGZylmzwCNI5izCGL39am1qRerSmBD7PPs3gT9MAVIHmEcU9gsnZiizxlG5L CLv+kWK/SPt76KevFkj5BQ9I2wlMrQKYZBQhKZbJwmHCsddwXO0UecqJYSMMXS/MZAGl zMVdhjqOXyI25bd+hojBHMhSLnQXsgpRqb4ZvD1khFDg7odigeDe7vgpb49Zo9anfwy5 mx3w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jmBJyRO2T5yHV98lFnJReDtxz4k59RvLFqn3fwWDkhA=; b=jjcmdOP9K4fxvdpLo60HNVL2g3jpBq0cNdVUIECeA2kfBu2rBmmjA8khKgRSKbljN6 TCADDPv+5TM67KWOSfIJddIZa+wf1PHFRb77bt0MRpRAVQZ3M/C57oJJtKwUDxeTfRgo ofpdX4Qzky7kkVq6x8c5QNrv+a4bmvihVTpRU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=jmBJyRO2T5yHV98lFnJReDtxz4k59RvLFqn3fwWDkhA=; b=rWiPDpnhkwdGYhiIADxDGuT9M5Oqc7JdAtKenx9dXF3d/mhi0KYlGcSB7Pkld/FScI 4AjPBpLP0G7ZRzto9/yohMR/eFVoAugO82zz+raciW7kuumIavJpDZlyqDJcr2CwyzI9 +eFk1wkGJWCOsIHuLsHaxbvHr7rCIF79ogpC11za1IUy8OkmfqKtf8SkrevmO8isHxWd KH7vWNzE3iUskUeyXxIFazs3ZmqMdi5qHcz5KYsGaoEr2S97av7uP7F1VXBYN8Jajq2r dLO7wsBHeJVMh0MoZPHHA6nSjBcbgLWvub41BEct4pODv9fOS4hNGG/8npsp4+SOoYfQ rngQ== X-Gm-Message-State: ALQs6tDmTcgN/J54ya11ZesqQ4NY76KZaEwdAkbDeMyBQV04j4aidaaC zCjuVOhIiSEM4Hv/1l5IEjEcS1PnQncTvn94Spjsgw== X-Received: by 10.31.168.213 with SMTP id r204mr2474571vke.84.1523588564521; Thu, 12 Apr 2018 20:02:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.164.81 with HTTP; Thu, 12 Apr 2018 20:02:43 -0700 (PDT) In-Reply-To: References: <10360653.ov98egbaqx@natalenko.name> <2864697.7uzmEJovl2@natalenko.name> From: Kees Cook Date: Thu, 12 Apr 2018 20:02:43 -0700 X-Google-Sender-Auth: FkdeRinnirnGHnAc31BG6wfMclM Message-ID: Subject: Re: usercopy whitelist woe in scsi_sense_cache To: Oleksandr Natalenko , Jens Axboe Cc: David Windsor , "James E.J. Bottomley" , "Martin K. Petersen" , linux-scsi@vger.kernel.org, LKML , Christoph Hellwig , Hannes Reinecke , Johannes Thumshirn , linux-block@vger.kernel.org, paolo.valente@linaro.org 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 Thu, Apr 12, 2018 at 3:47 PM, Kees Cook wrote: > After fixing up some build issues in the middle of the 4.16 cycle, I > get an unhelpful bisect result of commit 0a4b6e2f80aa ("Merge branch > 'for-4.16/block'"). Instead of letting the test run longer, I'm going > to switch to doing several shorter test boots per kernel and see if > that helps. One more bisect coming... Okay, so I can confirm the bisect points at the _merge_ itself, not a specific patch. I'm not sure how to proceed here. It looks like some kind of interaction between separate trees? Jens, do you have suggestions on how to track this down? -Kees -- Kees Cook Pixel Security