From: syzbot <syzbot+f775be4458668f7d220e@syzkaller.appspotmail.com>
To: alibuda@linux.alibaba.com, davem@davemloft.net,
dust.li@linux.alibaba.com, edumazet@google.com,
guwen@linux.alibaba.com, horms@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-s390@vger.kernel.org, mjambigi@linux.ibm.com,
netdev@vger.kernel.org, pabeni@redhat.com,
sidraya@linux.ibm.com, syzkaller-bugs@googlegroups.com,
tonylu@linux.alibaba.com, wangliang74@huawei.com,
wenjia@linux.ibm.com, yuehaibing@huawei.com,
zhangchangzhong@huawei.com
Subject: Re: [syzbot] [smc?] general protection fault in __smc_diag_dump (4)
Date: Fri, 19 Sep 2025 21:37:06 -0700 [thread overview]
Message-ID: <68ce2f72.050a0220.13cd81.000f.GAE@google.com> (raw)
In-Reply-To: <0ca2c567-b311-4f0b-bb29-2b860b75f85e@huawei.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file net/smc/smc.h
Hunk #1 FAILED at 285.
1 out of 1 hunk FAILED
Tested on:
commit: cd89d487 Merge tag '6.17-rc6-smb3-client-fixes' of git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8f01d8629880e620
dashboard link: https://syzkaller.appspot.com/bug?extid=f775be4458668f7d220e
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1381a0e2580000
next prev parent reply other threads:[~2025-09-20 4:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 17:58 [syzbot] [smc?] general protection fault in __smc_diag_dump (4) syzbot
2025-09-19 12:15 ` syzbot
2025-09-20 3:14 ` Wang Liang
2025-09-20 4:37 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-20 6:48 Wang Liang
2025-09-20 6:52 ` syzbot
2025-10-17 6:48 Wang Liang
2025-10-17 7:40 ` Wang Liang
2025-10-17 6:50 Wang Liang
2025-10-17 7:22 ` 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=68ce2f72.050a0220.13cd81.000f.GAE@google.com \
--to=syzbot+f775be4458668f7d220e@syzkaller.appspotmail.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tonylu@linux.alibaba.com \
--cc=wangliang74@huawei.com \
--cc=wenjia@linux.ibm.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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.