All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+938fcd548c303fe33c1a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: syz test
Date: Fri, 07 Nov 2025 12:06:26 -0800	[thread overview]
Message-ID: <690e5142.a70a0220.22f260.005e.GAE@google.com> (raw)
In-Reply-To: <68dc3dac.a00a0220.102ee.004f.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: syz test
Author: kriish.sharma2006@gmail.com

#syz test


 drivers/infiniband/core/addr.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/infiniband/core/addr.c b/drivers/infiniband/core/addr.c
index 61596cda2b65..f33d8040bbd5 100644
--- a/drivers/infiniband/core/addr.c
+++ b/drivers/infiniband/core/addr.c
@@ -93,13 +93,16 @@ static inline bool ib_nl_is_good_ip_resp(const
struct nlmsghdr *nlh)
  if (ret)
  return false;

+ if (!tb[LS_NLA_TYPE_DGID])
+ return -EINVAL;;
+
  return true;
 }

 static void ib_nl_process_good_ip_rsep(const struct nlmsghdr *nlh)
 {
  const struct nlattr *head, *curr;
- union ib_gid gid;
+ union ib_gid gid = {};
  struct addr_req *req;
  int len, rem;
  int found = 0;

  parent reply	other threads:[~2025-11-07 20:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 20:29 [syzbot] [rdma?] KMSAN: uninit-value in ib_nl_handle_ip_res_resp syzbot
2025-10-01  3:02 ` Kohei Enju
2025-10-02 18:16   ` yanjun.zhu
2025-10-02 18:31     ` Kohei Enju
2025-10-25 16:40 ` syzbot
2025-11-06 19:28 ` Forwarded: test syzbot
2025-11-06 19:45 ` Forwarded: syz test syzbot
2025-11-07 20:06 ` syzbot [this message]
2025-11-07 20:11 ` Forwarded: final test syzbot
2025-11-07 22:53 ` Forwarded: syz test syzbot
  -- strict thread matches above, loose matches on Subject: below --
2026-05-29 20:01 [syzbot] [netfs?] KASAN: slab-use-after-free Read in netfs_unbuffered_write syzbot
2026-05-30  2:13 ` Forwarded: #syz test syzbot
2026-04-09 18:30 [syzbot] [fuse?] BUG: scheduling while atomic in __synchronize_srcu syzbot
2026-04-13  4:40 ` Forwarded: #syz test syzbot
2026-04-13  4:49 ` syzbot
2026-04-13  4:50 ` syzbot
2026-04-13  4:52 ` syzbot
2026-04-13  5:08 ` syzbot
2026-04-13  6:04 ` syzbot
2026-04-30 16:06 ` syzbot
2026-04-30 17:26 ` syzbot
2026-04-30 17:41 ` syzbot
2026-04-30 18:27 ` syzbot
2026-04-30 18:53 ` syzbot
2025-08-27 21:55 [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
2025-09-20 10:59 ` Forwarded: syz test 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=690e5142.a70a0220.22f260.005e.GAE@google.com \
    --to=syzbot+938fcd548c303fe33c1a@syzkaller.appspotmail.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.