From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754935AbdLTJzk (ORCPT ); Wed, 20 Dec 2017 04:55:40 -0500 Received: from mail-it0-f70.google.com ([209.85.214.70]:39412 "EHLO mail-it0-f70.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754699AbdLTJzb (ORCPT ); Wed, 20 Dec 2017 04:55:31 -0500 X-Google-Smtp-Source: ACJfBosruxQEcFTZXoxyYF8dIkcMR6xw72opzOo9L3UqCXqe4jWcMrQJ5UO7fnOEDPaU4zaeFnJFnn3ebEWeY1/Pu1LjVyWHMPh0 MIME-Version: 1.0 Date: Wed, 20 Dec 2017 01:55:29 -0800 In-Reply-To: <18467907.EfXNf1iGip@tauon.chronox.de> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <001a1143d40c663a920560c295ca@google.com> Subject: Re: KASAN: use-after-free Read in crypto_aead_free_instance From: syzbot To: Stephan Mueller Cc: davem@davemloft.net, dvyukov@google.com, herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, smueller@chronox.de, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Am Mittwoch, 20. Dezember 2017, 10:50:10 CET schrieb Dmitry Vyukov: > Hi Dmitry, >> On Wed, Dec 20, 2017 at 10:29 AM, Stephan Mueller > wrote: >> > Am Mittwoch, 20. Dezember 2017, 10:19:43 CET schrieb Dmitry Vyukov: >> > >> > Hi Dmitry, >> > >> >> > This issue vanishes after applying the patch "[PATCH v2] crypto: >> AF_ALG >> >> > - >> >> > limit mask and type". >> >> >> >> Hi Stephan, >> >> >> >> syzbot does not understand arbitrary English prose, it only >> understands >> > >> > this: >> >> > Once a fix for this bug is merged into any tree, reply to this email >> >> > with: >> >> > #syz fix: exact-commit-title >> >> >> >> Let's tell it about the fix: >> >> >> >> #syz fix: crypto: AF_ALG - limit mask and type >> > >> > I have seen that this is the approach, but the fix is not yet in the >> tree. >> > I just want to let folks know that there is a patch. >> Ah, ok, sorry. It's just difficult to tell when there is a reason to >> not provide the tag right now, or when people are don't know about >> them or ignore. >> If the patch is merged with this title, then there is nothing else to >> do. If it's merged under a different title, a new "#syz fix:" tag will >> override the old one. > Maybe you can teach the syzcaller that there is a proposed fix? E.g. > #syz proposed: commit-title unknown command "proposed:" > Ciao > Stephan