lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 6 Oct 2022 09:35:19 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Dongliang Mu <mudongliangabcd@...il.com>
Cc:     syzbot <syzbot+5b129e8586277719bab3@...kaller.appspotmail.com>,
        dhowells@...hat.com, linux-cachefs-bounces@...hat.com,
        linux-cachefs-owner@...hat.com, linux-cachefs@...hat.com,
        linux-kernel@...r.kernel.org, nogikh@...gle.com,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] general protection fault in fscache_free_cookie

On Wed, 28 Sept 2022 at 11:23, Dongliang Mu <mudongliangabcd@...il.com> wrote:
>
> On Wed, Sep 28, 2022 at 5:15 PM syzbot
> <syzbot+5b129e8586277719bab3@...kaller.appspotmail.com> wrote:
> >
> > This bug is marked as fixed by commit:
> > fscache: fix GPF in fscache_free_cookie
> > But I can't find it in any tested tree for more than 90 days.
> > Is it a correct commit? Please update it by replying:
> > #syz fix: exact-commit-title
> > Until then the bug is still considered open and
> > new crashes with the same signature are ignored.
>
> @Dmitry Vyukov Why syzbot continuously complains about this bug
> report? The fix commit looks correct.


git log --grep "fscache: fix GPF in fscache_free_cookie"
on the latest upstream tree gives me nothing.

Where is this commit present? What's the git tree and commit hash?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ