From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B2355C00528 for ; Wed, 2 Aug 2023 20:00:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229741AbjHBUAe (ORCPT ); Wed, 2 Aug 2023 16:00:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52246 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229495AbjHBUAc (ORCPT ); Wed, 2 Aug 2023 16:00:32 -0400 Received: from netrider.rowland.org (netrider.rowland.org [192.131.102.5]) by lindbergh.monkeyblade.net (Postfix) with SMTP id 2FD491FFA for ; Wed, 2 Aug 2023 13:00:29 -0700 (PDT) Received: (qmail 217771 invoked by uid 1000); 2 Aug 2023 16:00:28 -0400 Date: Wed, 2 Aug 2023 16:00:28 -0400 From: Alan Stern To: Greg KH Cc: Khazhy Kumykov , syzbot , linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Re: [syzbot] [usb?] KASAN: slab-out-of-bounds Read in read_descriptors (3) Message-ID: <58e8a28b-ab24-4449-9072-e0fb7ed39196@rowland.harvard.edu> References: <0000000000007fc04d06011e274f@google.com> <248d9759-aef7-45ce-b0a4-6c1cafee76c9@rowland.harvard.edu> <2023072648-exclaim-crisply-9d8a@gregkh> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2023072648-exclaim-crisply-9d8a@gregkh> Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org Greg: I'm putting together a series of three patches to deal with this problem. The first two do some preparatory work, and the bug found by syzbot actually gets fixed by the third patch. In view of this, how should I tag the patches? They should all get into the -stable trees eventually, but only the third one really deserves a Fixes: or Reported-by: tag. What's your advice? Alan Stern