All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cie3ec19fdda59ffb3@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: tcp: fix use-after-free in do_tcp_getsockopt()
Date: Wed, 26 Aug 2026 11:37:57 -0700	[thread overview]
Message-ID: <6a8f3285.4d659fcc.734b4.0005.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] tcp: fix use-after-free in do_tcp_getsockopt()
https://lore.kernel.org/all/20260826171344.4133-1-blbllhy@gmail.com
* [PATCH net v2 1/2] tcp: fix use-after-free in do_tcp_getsockopt(TCP_CONGESTION)
* [PATCH net v2 2/2] tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/2f1649c0-f2ae-4dba-91fe-85e6de6ced71

***

kernel build error

tree:      linux-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base:      f967455fb2a5a2079b9eb5823e9ccf359174bf9f
arch:      amd64
compiler:  Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/d1a76ec6-f991-45ea-95a6-725073b26fb5/config

net/ipv4/tcp.c:4592:3: error: use of undeclared identifier 'ca_ops'; did you mean 'pv_ops'?
net/ipv4/tcp.c:4592:10: error: assigning to 'struct paravirt_patch_template' from incompatible type 'typeof_unqual (icsk->icsk_ca_ops)' (aka 'const struct tcp_congestion_ops *')
net/ipv4/tcp.c:4593:19: error: use of undeclared identifier 'ca_ops'; did you mean 'pv_ops'?
net/ipv4/tcp.c:4593:25: error: member reference type 'struct paravirt_patch_template' is not a pointer; did you mean to use '.'?
net/ipv4/tcp.c:4593:27: error: no member named 'name' in 'struct paravirt_patch_template'

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: syzbot@syzkaller.appspotmail.com

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

To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[andriin@fb.com ast@kernel.org autonomouscodesecurity@microsoft.com blbllhy@gmail.com bpf@vger.kernel.org davem@davemloft.net edumazet@google.com geliang@kernel.org horms@kernel.org kafai@fb.com kuba@kernel.org kuniyu@google.com kys@microsoft.com linux-kernel@vger.kernel.org martineau@kernel.org matttbe@kernel.org mptcp@lists.linux.dev ncardwell@google.com netdev@vger.kernel.org pabeni@redhat.com stable@vger.kernel.org tgopinath@linux.microsoft.com xmei5@asu.edu yhs@fb.com]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid


                 reply	other threads:[~2026-08-26 18:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6a8f3285.4d659fcc.734b4.0005.GAE@google.com \
    --to=syzbot+cie3ec19fdda59ffb3@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-upstream-moderation@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.