From: Rachel Sibley <rasibley@redhat.com>
To: netdev@vger.kernel.org
Cc: Jan Stancek <jstancek@redhat.com>
Subject: WARNING: CPU: 0 PID: 805 at net/core/dev.c:1595 dev_disable_lro+0xb2/0xf0
Date: Mon, 20 Apr 2020 14:23:58 -0400 [thread overview]
Message-ID: <a47b6a3b-c064-2f53-7cf6-d0d0720e9d99@redhat.com> (raw)
Hello,
Apologies if I'm sending to the wrong ML, hopefully this is the right place. During
podman[1] testing in CKI[2](Continuous Kernel Integration), we found a potential kernel
bug when running the "podman images - history output" test. An issue was filed against
libpod project [3], however it was later closed and advised to file a kernel bug instead.
Hoping someone can follow up or point me in the right direction.
Thanks,
Rachel
[1] https://github.com/CKI-project/tests-beaker/tree/master/container/podman
[2] https://cki-project.org/
[3] https://github.com/containers/libpod/issues/5815
reply other threads:[~2020-04-20 18:24 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=a47b6a3b-c064-2f53-7cf6-d0d0720e9d99@redhat.com \
--to=rasibley@redhat.com \
--cc=jstancek@redhat.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).