Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp337205imm; Thu, 5 Jul 2018 00:51:58 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcLb/Fb7G6P28zkCp4JKDTLcE6sMH7oKeRl2QtyoTmVz7feIjLVZHlMBD734ZsVpm2AOziy X-Received: by 2002:a17:902:904c:: with SMTP id w12-v6mr5075973plz.34.1530777118083; Thu, 05 Jul 2018 00:51:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530777118; cv=none; d=google.com; s=arc-20160816; b=McHYNlTRsFoWObLuuNepWkWy0aF9dF3HQw/MGXXJ3bXZRnFuROCFmPXq3O3bb0kzfN YHYhNoQwLXxo3XfpZlqtwhbow+qISg/yWkc3WNGF0T1w+JQCxXixqbe7/+AEi7e1VH2j h4N1sbI6F/zTMag0X2GirXFCLz5Fog+4S46mLQTlQe8pGMADOk7/gY0YNacpHVZTyV0Y RrezLyIM7C37Vlt+X+xfZKWgIFGWrbu2XHrnaSTR8gpNY232CaN1rKGR/YUKwc33IjOJ 1zuahhsg2DwzaeuTLLSjQh/hJ9K1xywQWgLj9NuEj/tl6WkP76YpXN1WdE57b6BRRyCA sNGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature:arc-authentication-results; bh=Y7dX1eQ63OZ912w2fdvynQAfsY39jx0SEe9D36k3qG0=; b=JrQ/Qt2pBDMrNCl9+IhLy9Ir165JjMerSyjvC1YMprYzk6U+MhptL61NAteh6OZfZc ua/gN3XholL7e5njIvtumvPVWRb8A9Lzl5MUEAQ5ErTBl6MiFzTqU9oBXQk6cgkrfwRs t0Qu8wTSwOggLEp8urYN3pw7mtth0vrQ3dm3aJJr10IUSWABVJBJ4v/6mX8UkqRKG3rW 6v0QTBgdKl1IrYT9LVilvNZEPlw/j7ijSIh+l8DkhVrgcR6dpr4jomySzH7iswsbjqb5 O/V1UW6X7fFck3EmuvuG7KHDAy3T956pcrMDmZFNC6r+9lpPkiL7G9X8t07MJYqQirrw 7sgA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@chronox.de header.s=strato-dkim-0002 header.b=WUYn6LN2; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f66-v6si5506608plb.103.2018.07.05.00.51.43; Thu, 05 Jul 2018 00:51:58 -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=@chronox.de header.s=strato-dkim-0002 header.b=WUYn6LN2; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753290AbeGEHtz (ORCPT + 99 others); Thu, 5 Jul 2018 03:49:55 -0400 Received: from mo4-p01-ob.smtp.rzone.de ([81.169.146.164]:12700 "EHLO mo4-p01-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753068AbeGEHtx (ORCPT ); Thu, 5 Jul 2018 03:49:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1530776991; s=strato-dkim-0002; d=chronox.de; h=References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=Y7dX1eQ63OZ912w2fdvynQAfsY39jx0SEe9D36k3qG0=; b=WUYn6LN2UwxTPN5FOPtIA7vdDLYsMa8rT76U9dfsLBbVgLtqw7tw1q1/x+JxxUJn98 zGIQ2gsgXJSdc6e4/Hai9RCETuL/xqZIRlOe6p0bUZPYtt80H+iXDS49mq0MxcNLkVkI 6GT2QBdtwEpHxwzZI/isHBIQXw/xXrLCe1VStoqSF5NE3KkJLEnsoG6ADaQiyUhhQ1Cd 2mH14jKwXuDARpXhnUTITqOEQC0CVT+qW8JwCm0qzPmXvOo31ln73xWsHuX+HCunmyDS BBnikprFEQEbLdck1LvNHJULqWwMnVMPvz2d/PefSfSsslunAEEuJSVy3VTHX+KxZxra vPDw== X-RZG-AUTH: ":P2ERcEykfu11Y98lp/T7+hdri+uKZK8TKWEqNyiHySGSa9k9zT8DNpa83PTIZWvq/+MyXt/DL7dI0Ihg0SicdGB/Mshf6dqAJJ4h" X-RZG-CLASS-ID: mo00 Received: from positron.chronox.de by smtp.strato.de (RZmta 43.12 AUTH) with ESMTPSA id t07687u657nl6K7 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Thu, 5 Jul 2018 09:49:47 +0200 (CEST) From: Stephan =?ISO-8859-1?Q?M=FCller?= To: Eric Biggers Cc: Dmitry Vyukov , syzbot , David Miller , Herbert Xu , linux-crypto@vger.kernel.org, LKML , syzkaller-bugs@googlegroups.com Subject: Re: [PATCH] AF_ALG: register completely initialized request in list Date: Thu, 05 Jul 2018 09:49:41 +0200 Message-ID: <3179058.YavDkrnvkQ@positron.chronox.de> In-Reply-To: <20180704233757.GK725@sol.localdomain> References: <00000000000092ad87056950ef9e@google.com> <3223691.KS9TZr8pPl@tauon.chronox.de> <20180704233757.GK725@sol.localdomain> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Donnerstag, 5. Juli 2018, 01:37:57 CEST schrieb Eric Biggers: Hi Eric, > On Mon, Apr 09, 2018 at 09:54:12AM +0200, Stephan Mueller wrote: > > Am Montag, 9. April 2018, 09:51:13 CEST schrieb Dmitry Vyukov: > > > > Hi Dmitry, > > > > > You can ask syzbot to test by replying to its report email with a test > > > command, see: > > > https://github.com/google/syzkaller/blob/master/docs/syzbot.md#communica > > > tion -with-syzbot > > > > > > Note that all testing of KMSAN bugs needs to go to KMSAN tree, for > > > details > > > see: > > > https://github.com/google/syzkaller/blob/master/docs/syzbot.md#kmsan-bug > > > s > > > > Thank you. I will resend the patch later today with the proper tags. > > > > Ciao > > Stephan > > Hi Stephan, it seems you never sent your patch out. Thank you for pointing this one out. At the time, I was searching for how I can refer to the syzbot KMSAN branch that was used to produce the bug report. I only see guidance on how to point to the Linux kernel tree. Do you have a hint how to point to a different syzbot tree? Ciao Stephan