[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230307010824.foxfdlhvuqc43dex@begin>
Date: Tue, 7 Mar 2023 02:08:24 +0100
From: Samuel Thibault <samuel.thibault@...-lyon.org>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: Kees Cook <keescook@...omium.org>,
syzbot <syzbot+3af17071816b61e807ed@...kaller.appspotmail.com>,
akpm@...ux-foundation.org, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
syzkaller-bugs@...glegroups.com, Jiri Slaby <jirislaby@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [syzbot] [hardening?] [mm?] BUG: bad usercopy in con_font_op
Aleksandr Nogikh, le lun. 06 mars 2023 11:28:04 +0100, a ecrit:
> On Mon, Mar 6, 2023 at 8:36 AM Samuel Thibault
> <samuel.thibault@...-lyon.org> 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
Powered by blists - more mailing lists