public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d31adfb277377ef8fcba@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [iommu?] KASAN: slab-use-after-free Read in iommufd_vfio_ioas
Date: Fri, 03 Nov 2023 01:08:04 -0700	[thread overview]
Message-ID: <000000000000f75b0c06093b006d@google.com> (raw)
In-Reply-To: <20231103075800.3488232-1-lizhi.xu@windriver.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

./include/linux/stddef.h:8:14: error: incompatible types when assigning to type 'struct iommufd_object' from type 'void *'


Tested on:

commit:         2af9b20d Merge tag 'x86-urgent-2023-10-28' of git://gi..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=cb98fe061049a6e4
dashboard link: https://syzkaller.appspot.com/bug?extid=d31adfb277377ef8fcba
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=178165a0e80000


       reply	other threads:[~2023-11-03  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231103075800.3488232-1-lizhi.xu@windriver.com>
2023-11-03  8:08 ` syzbot [this message]
     [not found] <20231103114509.1232-1-hdanton@sina.com>
2023-11-03 12:15 ` [syzbot] [iommu?] KASAN: slab-use-after-free Read in iommufd_vfio_ioas syzbot
     [not found] <20231103070938.2846226-1-lizhi.xu@windriver.com>
2023-11-03  7:16 ` syzbot
     [not found] <20231103053639.1095013-1-lizhi.xu@windriver.com>
2023-11-03  5:52 ` syzbot
     [not found] <20231103011803.3249005-1-lizhi.xu@windriver.com>
2023-11-03  4:08 ` syzbot
2023-11-02 23:03 syzbot

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=000000000000f75b0c06093b006d@google.com \
    --to=syzbot+d31adfb277377ef8fcba@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.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