From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755040AbdLTLtv (ORCPT ); Wed, 20 Dec 2017 06:49:51 -0500 Received: from mail.eperm.de ([89.247.134.16]:44474 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754692AbdLTLtu (ORCPT ); Wed, 20 Dec 2017 06:49:50 -0500 From: Stephan Mueller To: Dmitry Vyukov Cc: syzbot , David Miller , Herbert Xu , linux-crypto@vger.kernel.org, LKML , syzkaller-bugs@googlegroups.com Subject: Re: KASAN: use-after-free Read in crypto_aead_free_instance Date: Wed, 20 Dec 2017 12:49:47 +0100 Message-ID: <12415329.MInO136rYd@tauon.chronox.de> In-Reply-To: References: <001a11c14bc887c2c60560c0cdda@google.com> <18467907.EfXNf1iGip@tauon.chronox.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, 20. Dezember 2017, 11:15:38 CET schrieb Dmitry Vyukov: Hi Dmitry, > > What will be its meaning? How will it differ from fix? Maybe a short clarification would help: what is the meaning of the syz fix marker? Depending on this answer, all that I am thinking of is to mark bug reports for which there are fixes actively discussed, but yet not integrated. Thus, such marker should only help others to point them to active discussions instead of them trying to find fixes alone. Ciao Stephan