From: syzbot ci <syzbot+ci665f7953cbbac48d@syzkaller.appspotmail.com>
To: andrew@lunn.ch, davem@davemloft.net, dskr99@gmail.com,
edumazet@google.com, kees@kernel.org,
krystianmkaniewski@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzbot@lists.linux.dev,
syzbot@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: ipvlan: keep lower device alive until private destruction
Date: Mon, 03 Aug 2026 09:57:10 -0700 [thread overview]
Message-ID: <6a70c866.2d659fcc.1d46f5.01ec.GAE@google.com> (raw)
In-Reply-To: <20260803121140.261329-1-krystianmkaniewski@gmail.com>
syzbot ci has tested the following series
[v2] ipvlan: keep lower device alive until private destruction
https://lore.kernel.org/all/20260803121140.261329-1-krystianmkaniewski@gmail.com
* [PATCH net v2] ipvlan: keep lower device alive until private destruction
and found no issues.
Full report is available here:
https://ci.syzbot.org/series/33f00e49-faea-4860-a29a-c8b4792c5338
***
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.
prev parent reply other threads:[~2026-08-03 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 12:11 [PATCH net v2] ipvlan: keep lower device alive until private destruction Krystian Kaniewski
2026-08-03 16:57 ` syzbot ci [this message]
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=6a70c866.2d659fcc.1d46f5.01ec.GAE@google.com \
--to=syzbot+ci665f7953cbbac48d@syzkaller.appspotmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dskr99@gmail.com \
--cc=edumazet@google.com \
--cc=kees@kernel.org \
--cc=krystianmkaniewski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox