All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci56a328c65c235c77@syzkaller.appspotmail.com>
To: syzbot@syzkaller.appspotmail.com, mjambigi@linux.ibm.com,
	 syzbot@lists.linux.dev
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: net/smc: fix clcsock and lgr/lnk races in smc_diag dump path
Date: Wed, 12 Aug 2026 06:22:32 -0700	[thread overview]
Message-ID: <6a7c7398.c5ad36c8.12f49d.0028.GAE@google.com> (raw)
In-Reply-To: <6a7c692e.d5f0ebe7.22d851.000c.GAE@google.com>

syzbot ci has tested the suggested fix patch on top of the following series:

[v3] net/smc: fix clcsock and lgr/lnk races in smc_diag dump path
https://lore.kernel.org/all/20260807081606.3200128-1-mjambigi@linux.ibm.com

Patch: https://ci.syzbot.org/jobs/0c1c7e8f-103f-49ac-9196-1a291971a9cd/patch
Testing results:
* [build 0] Build Patched: passed
* [build 0] Boot test: Patched: passed
* [build 0] Previous reproducers: passed
  - WARNING in smc_diag_dump_proto (patched) - passed

Full report is available here:
https://ci.syzbot.org/session/f5a9f860-ef52-446f-a775-661f3e756d37

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

  reply	other threads:[~2026-08-12 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <df7a4fe7-d9be-4a5d-942b-5ca3c1fb1031@linux.ibm.com>
2026-08-12 12:38 ` Forwarded: Re: [syzbot ci] Re: net/smc: fix clcsock and lgr/lnk races in smc_diag dump path syzbot
2026-08-12 13:22   ` syzbot ci [this message]
2026-08-07  8:16 [PATCH net v3] " Mahanta Jambigi
2026-08-07 15:02 ` [syzbot ci] " syzbot ci
2026-08-11  8:03   ` Mahanta Jambigi
2026-08-11  8:09     ` syzbot ci

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=6a7c7398.c5ad36c8.12f49d.0028.GAE@google.com \
    --to=syzbot+ci56a328c65c235c77@syzkaller.appspotmail.com \
    --cc=mjambigi@linux.ibm.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzbot@syzkaller.appspotmail.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.