From: Jann Horn <jannh@google.com>
To: amir73il@gmail.com,
syzbot <syzbot+477d8d8901756d1cbba1@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] KASAN: invalid-free in ovl_copy_up_one
Date: Fri, 24 Nov 2023 16:11:54 +0100 [thread overview]
Message-ID: <CAG48ez2UkCR7LMaQfCQVLW4VOZG9CuPDMHG7cBtaAitM=zPBCg@mail.gmail.com> (raw)
In-Reply-To: <000000000000258ac60606589787@google.com>
On Wed, Sep 27, 2023 at 5:10 PM syzbot
<syzbot+477d8d8901756d1cbba1@syzkaller.appspotmail.com> wrote:
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-and-tested-by: syzbot+477d8d8901756d1cbba1@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 8e9b46c4 ovl: do not encode lower fh with upper sb_wri..
> git tree: https://github.com/amir73il/linux.git ovl_want_write
> console output: https://syzkaller.appspot.com/x/log.txt?x=10d10ffa680000
> kernel config: https://syzkaller.appspot.com/x/.config?x=bb54ecdfa197f132
> dashboard link: https://syzkaller.appspot.com/bug?extid=477d8d8901756d1cbba1
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
It looks like the fix was submitted without the Reported-by tag, so
syzkaller doesn't recognize that the fix has landed... I'll tell
syzkaller now which commit the fix is supposed to be in, please
correct me if this is wrong:
#syz fix: ovl: do not encode lower fh with upper sb_writers held
next prev parent reply other threads:[~2023-11-24 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 0:50 [syzbot] [overlayfs?] KASAN: invalid-free in ovl_copy_up_one syzbot
2023-09-27 14:41 ` Amir Goldstein
2023-09-27 15:10 ` syzbot
2023-11-24 15:11 ` Jann Horn [this message]
2023-11-24 15:26 ` Jann Horn
2023-11-25 9:21 ` Amir Goldstein
2023-11-25 9:21 ` syzbot
2023-11-25 11:50 ` Jann Horn
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='CAG48ez2UkCR7LMaQfCQVLW4VOZG9CuPDMHG7cBtaAitM=zPBCg@mail.gmail.com' \
--to=jannh@google.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=syzbot+477d8d8901756d1cbba1@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).