linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+8c3af233123df0578a5c@syzkaller.appspotmail.com>
Cc: ebiederm@xmission.com, legion@kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Write in get_ucounts
Date: Fri, 17 Sep 2021 09:53:57 +0200	[thread overview]
Message-ID: <CACT4Y+b1YFQLeZkH8z_n_-x7s6jmY-p=07vJk89-KZgQXYs1sQ@mail.gmail.com> (raw)
In-Reply-To: <000000000000b1e03005cb6230b5@google.com>

On Tue, 7 Sept 2021 at 08:51, syzbot
<syzbot+8c3af233123df0578a5c@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 345daff2e994ee844d6a609c37f085695fbb4c4d
> Author: Alexey Gladkov <legion@kernel.org>
> Date:   Tue Jul 27 15:24:18 2021 +0000
>
>     ucounts: Fix race condition between alloc_ucounts and put_ucounts
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1378d0ed300000
> start commit:   d5ad8ec3cfb5 Merge tag 'media/v5.14-2' of git://git.kernel..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=702bfdfbf389c324
> dashboard link: https://syzkaller.appspot.com/bug?extid=8c3af233123df0578a5c
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16fedec6300000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: ucounts: Fix race condition between alloc_ucounts and put_ucounts

Looks legit:

#syz fix: ucounts: Fix race condition between alloc_ucounts and put_ucounts

      reply	other threads:[~2021-09-17  7:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  7:56 [syzbot] KASAN: use-after-free Write in get_ucounts syzbot
2021-09-07  6:51 ` syzbot
2021-09-17  7:53   ` Dmitry Vyukov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACT4Y+b1YFQLeZkH8z_n_-x7s6jmY-p=07vJk89-KZgQXYs1sQ@mail.gmail.com' \
    --to=dvyukov@google.com \
    --cc=ebiederm@xmission.com \
    --cc=legion@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+8c3af233123df0578a5c@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).