linux-kernel - Re: [syzbot] linux-next build error (24)

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] [day] [month] [year] [list]

Message-ID: <CANp29Y4L45Z1OK6mS2rGwHmA-0CP2a0qD7G3NCz=CcbqEFNUyQ@mail.gmail.com>
Date: Tue, 4 Nov 2025 10:22:55 +0100
From: Aleksandr Nogikh <nogikh@...gle.com>
To: syzbot <syzbot+c78a89917a1b7c0fa4c6@...kaller.appspotmail.com>, 
	rust-for-linux@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, 
	sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] linux-next build error (24)

+ rust-for-linux

On Tue, Nov 4, 2025 at 10:17 AM syzbot
<syzbot+c78a89917a1b7c0fa4c6@...kaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    982312090977 Add linux-next specific files for 20251103
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=110f817c580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=1cf6c387ad3e8e7a
> dashboard link: https://syzkaller.appspot.com/bug?extid=c78a89917a1b7c0fa4c6
> compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+c78a89917a1b7c0fa4c6@...kaller.appspotmail.com
>
> error[E0599]: no method named `data` found for struct `core::pin::Pin<kbox::Box<T, Kmalloc>>` in the current scope
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@...glegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
>
> If you want to overwrite report's subsystems, reply with:
> #syz set subsystems: new-subsystem
> (See the list of subsystem names on the web dashboard)
>
> If the report is a duplicate of another one, reply with:
> #syz dup: exact-subject-of-another-report
>
> If you want to undo deduplication, reply with:
> #syz undup
>