All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci0bbe7d78854ef9f6@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: devmem: improve cpu cost of RX token management
Date: Fri, 26 Sep 2025 08:43:22 -0700	[thread overview]
Message-ID: <68d6b49a.050a0220.3390a8.0016.GAE@google.com> (raw)

syzbot ci has tested the following series

[v3] net: devmem: improve cpu cost of RX token management
https://lore.kernel.org/all/20250926-scratch-bobbyeshleman-devmem-tcp-token-upstream-v3-0-084b46bda88f@meta.com
* [PATCH net-next v3 1/2] net: devmem: rename tx_vec to vec in dmabuf binding
* [PATCH net-next v3 2/2] net: devmem: use niov array for token management

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/e81af5ec-56ef-4ac8-b819-b7c693a9f977

***

kernel build error

tree:      net
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base:      4ff71af020ae59ae2d83b174646fc2ad9fcd4dc4
arch:      amd64
compiler:  Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config:    https://ci.syzbot.org/builds/966856af-5973-4648-b78a-9571e11b4205/config

net/core/sock.c:1124:36: error: no member named 'sk_user_frags' in 'struct sock'

***

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.

The email will later be sent to:
[almasrymina@google.com bobbyeshleman@gmail.com bobbyeshleman@meta.com davem@davemloft.net dsahern@kernel.org edumazet@google.com horms@kernel.org kuba@kernel.org kuniyu@google.com linux-kernel@vger.kernel.org ncardwell@google.com netdev@vger.kernel.org pabeni@redhat.com sdf@fomichev.me willemb@google.com]

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


             reply	other threads:[~2025-09-26 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 15:43 syzbot ci [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-26 21:16 [moderation/CI] Re: net: devmem: improve cpu cost of RX token management syzbot ci
2025-09-27  5:58 ` Aleksandr Nogikh
2025-09-12  9:13 syzbot ci
2025-09-12  9:37 ` Aleksandr Nogikh
2025-09-03 16:14 syzbot ci
2025-09-03 17:43 ` Aleksandr Nogikh

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=68d6b49a.050a0220.3390a8.0016.GAE@google.com \
    --to=syzbot+ci0bbe7d78854ef9f6@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.