From: syzbot <syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KMSAN: kernel-infoleak in __skb_datagram_iter (4)
Date: Wed, 06 Nov 2024 14:19:05 -0800 [thread overview]
Message-ID: <672beb59.050a0220.350062.027d.GAE@google.com> (raw)
In-Reply-To: <CANn89iJptb2gackja+KocyPYwf855EgZM34GSO3km4Z8tcwq1w@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file include/uapi/linux/tc_act/tc_connmark.h
patch: **** malformed patch at line 11: diff --git a/include/uapi/linux/tc_act/tc_ife.h
Tested on:
commit: f43b1569 Merge tag 'keys-next-6.12-rc7' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6fdf74cce377223b
dashboard link: https://syzkaller.appspot.com/bug?extid=0c85cae3350b7d486aee
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=14119f40580000
next prev parent reply other threads:[~2024-11-06 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 12:51 [syzbot] [net?] KMSAN: kernel-infoleak in __skb_datagram_iter (4) syzbot
2024-11-06 17:58 ` syzbot
2024-11-06 18:09 ` Eric Dumazet
2024-11-06 22:19 ` syzbot [this message]
2025-10-31 9:49 ` Forwarded: test patch for KMSAN: kernel-infoleak in __skb_datagram_iter syzbot
2025-11-05 9:03 ` Forwarded: KMSAN: kernel-infoleak in __skb_datagram_iter (4) syzbot
[not found] <CAMz+-COzOAULnhRPuM=LeXzzG0n5VdbzfDhamiHak9FJaSWxfA@mail.gmail.com>
2025-10-31 11:18 ` [syzbot] [net?] " syzbot
[not found] <CAMz+-CPLgSojr8wHHY1Wdef+UUHBpVB9xWTYwZ-c0tQ41Trh2g@mail.gmail.com>
2025-11-05 9:32 ` 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=672beb59.050a0220.350062.027d.GAE@google.com \
--to=syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.