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 80FE6C6FA99 for ; Tue, 7 Mar 2023 01:08:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229737AbjCGBIb (ORCPT ); Mon, 6 Mar 2023 20:08:31 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38852 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229570AbjCGBI3 (ORCPT ); Mon, 6 Mar 2023 20:08:29 -0500 Received: from sonata.ens-lyon.org (domu-toccata.ens-lyon.fr [140.77.166.138]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CCEA330B04; Mon, 6 Mar 2023 17:08:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by sonata.ens-lyon.org (Postfix) with ESMTP id 6FCD62012C; Tue, 7 Mar 2023 02:08:25 +0100 (CET) Received: from sonata.ens-lyon.org ([127.0.0.1]) by localhost (sonata.ens-lyon.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPqUQ-mWdehP; Tue, 7 Mar 2023 02:08:25 +0100 (CET) Received: from begin.home (lfbn-bor-1-1163-184.w92-158.abo.wanadoo.fr [92.158.138.184]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by sonata.ens-lyon.org (Postfix) with ESMTPSA id 1360D200EE; Tue, 7 Mar 2023 02:08:25 +0100 (CET) Received: from samy by begin.home with local (Exim 4.96) (envelope-from ) id 1pZLoW-001GOs-1z; Tue, 07 Mar 2023 02:08:24 +0100 Date: Tue, 7 Mar 2023 02:08:24 +0100 From: Samuel Thibault To: Aleksandr Nogikh Cc: Kees Cook , syzbot , akpm@linux-foundation.org, linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, Jiri Slaby , Greg Kroah-Hartman Subject: Re: [syzbot] [hardening?] [mm?] BUG: bad usercopy in con_font_op Message-ID: <20230307010824.foxfdlhvuqc43dex@begin> Mail-Followup-To: Samuel Thibault , Aleksandr Nogikh , Kees Cook , syzbot , akpm@linux-foundation.org, linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, Jiri Slaby , Greg Kroah-Hartman References: <0000000000001d1fb505f605c295@google.com> <64026f89.170a0220.7940.49ff@mx.google.com> <20230305175457.kp6b5lmwwdxw4ii6@begin> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: I am not organized User-Agent: NeoMutt/20170609 (1.8.3) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Aleksandr Nogikh, le lun. 06 mars 2023 11:28:04 +0100, a ecrit: > On Mon, Mar 6, 2023 at 8:36 AM Samuel Thibault > wrote: > > > > The patch below should be fixing it, could you check? > > > > I don't know how I am supposed to properly reference the syzbot report > > etc., could somebody used to the process handle submitting the fix? > > As Jiri Slaby correctly said above, you just need to add the > `Reported-by` tag from the syzbot bug report to your patch so that the > bot can recognize the fix later. > > If you just want syzbot to check whether the reproducer still triggers > the bug after your changes, you can send an email with the `syz test` > command and the raw diff patch. Here are the instructions: > https://github.com/google/syzkaller/blob/master/docs/syzbot.md#testing-patches > and here are many examples: > https://groups.google.com/g/syzkaller-bugs/search?q=%22%23syz%20test%22 Thanks! The patch does fix the reproducer case. Samuel