From: David Ahern <dsahern@gmail.com>
To: willemb@google.com, "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: panic at sock_zerocopy_put when I ssh into a VM
Date: Tue, 8 Aug 2017 19:14:27 -0600 [thread overview]
Message-ID: <9ea97b60-7416-bdb2-e167-8fcc8c11b1cc@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
Willem:
I updated my host server this morning to top of net-next -- commit
53b948356554. I am not doing anything fancy or intentionally using the
zerocopy code. I launch a VM with vhost and attempt to login via ssh.
Doing that triggers a panic in the host at sock_zerocopy_put. The
attached is a snapshot of the console -- best I can get for the stack trace.
David
[-- Attachment #2: bt.jpg --]
[-- Type: image/jpeg, Size: 566366 bytes --]
next reply other threads:[~2017-08-09 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 1:14 David Ahern [this message]
2017-08-09 4:48 ` panic at sock_zerocopy_put when I ssh into a VM Willem de Bruijn
2017-08-09 5:01 ` Willem de Bruijn
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=9ea97b60-7416-bdb2-e167-8fcc8c11b1cc@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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