public inbox for syzbot@lists.linux.dev
 help / color / mirror / Atom feed
* [moderation/CI] Re: net: ifb: record drop reason when redirect device is missing
@ 2026-02-02 21:17 syzbot ci
  0 siblings, 0 replies; 3+ messages in thread
From: syzbot ci @ 2026-02-02 21:17 UTC (permalink / raw)
  To: syzkaller-upstream-moderation; +Cc: syzbot

syzbot ci has tested the following series

[v1] net: ifb: record drop reason when redirect device is missing
https://lore.kernel.org/all/20260202191135.7668-1-murariprasadsamal57@gmail.com
* [PATCH] net: ifb: record drop reason when redirect device is missing

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/d7d816eb-4146-4491-81b2-e48b630b1f8d

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      40cb4cb77ea26d65156f0442c846d5f7ff497839
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/1f29e847-a783-455b-a6aa-476a9e74ca65/config

drivers/net/ifb.c:118:26: error: use of undeclared identifier 'SKB_DROP_REASON_NO_DEV'; did you mean 'SKB_DROP_REASON_NOMEM'?

***

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:
[andrew@lunn.ch davem@davemloft.net edumazet@google.com kuba@kernel.org murariprasadsamal57@gmail.com netdev@vger.kernel.org pabeni@redhat.com]

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

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [moderation/CI] Re: net: ifb: record drop reason when redirect device is missing
@ 2026-02-03  7:48 syzbot ci
  0 siblings, 0 replies; 3+ messages in thread
From: syzbot ci @ 2026-02-03  7:48 UTC (permalink / raw)
  To: syzkaller-upstream-moderation; +Cc: syzbot

syzbot ci has tested the following series

[v3] net: ifb: record drop reason when redirect device is missing
https://lore.kernel.org/all/20260203060907.993-1-murariprasadsamal57@gmail.com
* [PATCH v3] net: ifb: record drop reason when redirect device is missing

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/8ff554d3-498c-4ade-b161-27c981248b40

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      40cb4cb77ea26d65156f0442c846d5f7ff497839
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/7367eec5-7ff7-4b94-a153-18c91d440f01/config

drivers/net/ifb.c:118:26: error: use of undeclared identifier 'SKB_DROP_REASON_NO_DEV'; did you mean 'SKB_DROP_REASON_NOMEM'?

***

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:
[andrew@lunn.ch davem@davemloft.net edumazet@google.com kuba@kernel.org murariprasadsamal57@gmail.com netdev@vger.kernel.org pabeni@redhat.com]

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

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [moderation/CI] Re: net: ifb: record drop reason when redirect device is missing
@ 2026-02-03  7:49 syzbot ci
  0 siblings, 0 replies; 3+ messages in thread
From: syzbot ci @ 2026-02-03  7:49 UTC (permalink / raw)
  To: syzkaller-upstream-moderation; +Cc: syzbot

syzbot ci has tested the following series

[v2] net: ifb: record drop reason when redirect device is missing
https://lore.kernel.org/all/20260203060415.886-1-murariprasadsamal57@gmail.com
* [PATCH v2] net: ifb: record drop reason when redirect device is missing

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/b1aa8cf9-0498-4c3d-8ecc-d0fed4f173a8

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      40cb4cb77ea26d65156f0442c846d5f7ff497839
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/fc702d8f-ebba-4f02-901b-3c50604fd8e3/config

drivers/net/ifb.c:118:26: error: use of undeclared identifier 'SKB_DROP_REASON_NO_DEV'; did you mean 'SKB_DROP_REASON_NOMEM'?

***

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:
[andrew@lunn.ch davem@davemloft.net edumazet@google.com kuba@kernel.org murariprasadsamal57@gmail.com netdev@vger.kernel.org pabeni@redhat.com]

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

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-02-03  7:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-02 21:17 [moderation/CI] Re: net: ifb: record drop reason when redirect device is missing syzbot ci
  -- strict thread matches above, loose matches on Subject: below --
2026-02-03  7:48 syzbot ci
2026-02-03  7:49 syzbot ci

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox