All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+477d8d8901756d1cbba1@syzkaller.appspotmail.com>
To: amir73il@gmail.com, 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: Wed, 27 Sep 2023 08:10:22 -0700	[thread overview]
Message-ID: <000000000000258ac60606589787@google.com> (raw)
In-Reply-To: <CAOQ4uxjssgw1tZrUQvtHHVacSgR9NE0yF8DA3+R5LNFAocCvVQ@mail.gmail.com>

Hello,

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

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2023-09-27 15:10 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 [this message]
2023-11-24 15:11     ` Jann Horn
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=000000000000258ac60606589787@google.com \
    --to=syzbot+477d8d8901756d1cbba1@syzkaller.appspotmail.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.