From: syzbot <syzbot+bbe84a4010eeea00982d@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [nfc?] KASAN: slab-use-after-free Read in nfc_alloc_send_skb
Date: Thu, 09 Nov 2023 05:02:04 -0800 [thread overview]
Message-ID: <0000000000007323f20609b7cfbb@google.com> (raw)
In-Reply-To: <tencent_226A496623B3645B9762576606DE537BE305@qq.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
net/nfc/nci/core.c:1210:30: error: static assertion failed due to requirement '__builtin_types_compatible_p(struct nfc_dev, struct nfc_dev *) || __builtin_types_compatible_p(struct nfc_dev, void)': pointer type mismatch in container_of()
Tested on:
commit: aea6bf90 Merge tag 'f2fs-for-6.7-rc1' of git://git.ker..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=93ac5233c138249e
dashboard link: https://syzkaller.appspot.com/bug?extid=bbe84a4010eeea00982d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1750e11f680000
next parent reply other threads:[~2023-11-09 13:02 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_226A496623B3645B9762576606DE537BE305@qq.com>
2023-11-09 13:02 ` syzbot [this message]
2023-11-09 13:28 ` [syzbot] [PATCH] Test for aea6bf908d73 syzbot
2023-11-09 14:14 ` syzbot
2023-11-09 14:33 ` syzbot
2023-11-09 19:04 ` [syzbot] [PATCH] Fix the null pointer deference in nsim_setup_prog_hw_checks syzbot
2023-11-10 0:52 ` [syzbot] [PATCH] test aea6bf908d73 syzbot
2023-11-10 6:32 ` syzbot
2023-11-10 11:26 ` [syzbot] [PATCH] Test for aea6bf908d73 syzbot
2023-11-10 12:19 ` syzbot
[not found] <tencent_EA64176726C1D373637A296B63AB444FD705@qq.com>
2023-11-10 12:47 ` [syzbot] [net?] [nfc?] KASAN: slab-use-after-free Read in nfc_alloc_send_skb syzbot
[not found] <20231110113921.1500-1-hdanton@sina.com>
2023-11-10 12:19 ` syzbot
[not found] <tencent_86284A9674717691670C3DBF360C96CA3609@qq.com>
2023-11-10 11:56 ` syzbot
[not found] <20231110063236.964222-1-lizhi.xu@windriver.com>
2023-11-10 9:57 ` syzbot
[not found] <20231110005229.2333509-1-lizhi.xu@windriver.com>
2023-11-10 1:12 ` syzbot
[not found] <20231109190331.107211-1-kdipendra88@gmail.com>
2023-11-09 19:19 ` syzbot
[not found] <tencent_EA791774C6CBD367236D297003A84441F705@qq.com>
2023-11-09 14:51 ` syzbot
[not found] <tencent_F3556E8C96D4E90EEEAACFF07A626DBC2D0A@qq.com>
2023-11-09 14:30 ` syzbot
[not found] <tencent_074AC2742F77F567E83C53362096E4365C09@qq.com>
2023-11-09 13:51 ` syzbot
2023-11-09 8:36 syzbot
2023-11-13 12:04 ` Siddh Raman Pant
2023-11-13 13:33 ` syzbot
2023-11-13 12:43 ` Siddh Raman Pant
2023-11-13 13:48 ` syzbot
2023-11-14 12:06 ` Siddh Raman Pant
2023-11-14 12:31 ` syzbot
2023-11-16 16:55 ` Siddh Raman Pant
2023-11-17 12:48 ` Krzysztof Kozlowski
2023-11-17 13:17 ` Siddh Raman Pant
2023-11-25 17:17 ` Siddh Raman Pant
2023-11-25 17:33 ` syzbot
2023-11-25 18:18 ` Siddh Raman Pant
2023-11-25 18:54 ` syzbot
2023-11-25 19:06 ` Siddh Raman Pant
2023-11-25 19:45 ` syzbot
2023-12-02 14:12 ` Siddh Raman Pant
2023-12-02 14:37 ` syzbot
2023-12-02 14:14 ` Siddh Raman Pant
2023-12-02 14:56 ` syzbot
2023-12-03 18:22 ` Siddh Raman Pant
2023-12-03 18:46 ` syzbot
2023-12-09 9:27 ` Siddh Raman Pant
2023-12-09 9:44 ` syzbot
2023-12-09 9:55 ` Siddh Raman Pant
2023-12-09 10:20 ` syzbot
2023-12-09 10:39 ` Siddh Raman Pant
2023-12-09 11:03 ` syzbot
2023-12-11 8:44 ` Paolo Abeni
2023-12-12 18:11 ` Siddh Raman Pant
2023-12-12 18:48 ` syzbot
2023-12-17 12:40 ` Siddh Raman Pant
2023-12-17 13:08 ` syzbot
2023-12-18 19:00 ` Siddh Raman Pant
2023-12-19 1:26 ` 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=0000000000007323f20609b7cfbb@google.com \
--to=syzbot+bbe84a4010eeea00982d@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--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.