Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ciaae744690cd95ee5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: leave O_NONBLOCK to the sendmsg and recvmsg syscalls
Date: Mon, 09 Nov 2026 22:42:19 -0800	[thread overview]
Message-ID: <6af2bccb.f27d6985.26ae05.004b.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] net: leave O_NONBLOCK to the sendmsg and recvmsg syscalls
https://lore.kernel.org/all/f084de67-85b0-4759-845f-513879ebee5f@kernel.dk
* [PATCH] net: leave O_NONBLOCK to the sendmsg and recvmsg syscalls

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/4835d68c-fc3f-41c6-9499-8a9de6613c8c

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      dce8f33934591b405067149ea4603ec89c878a6f
arch:      amd64
compiler:  Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/5113e912-7848-4b30-a836-740c8331eae2/config

make[3]: *** No rule to make target 'net/socket.o', needed by 'net/built-in.a'.  Stop.

***

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:
[axboe@kernel.dk edumazet@kernel.org kuba@kernel.org kuniyu@google.com netdev@vger.kernel.org pabeni@redhat.com willemb@google.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-11-10  6:42 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=6af2bccb.f27d6985.26ae05.004b.GAE@google.com \
    --to=syzbot+ciaae744690cd95ee5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox