From: Jakub Kicinski <kuba@kernel.org>
To: "Junichi Uekawa (上川純一) " <uekawa@chromium.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Eric Dumazet <edumazet@google.com>,
davem@davemloft.net, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org,
Bobby Eshleman <bobby.eshleman@gmail.com>
Subject: Re: [PATCH] vhost/vsock: Use kvmalloc/kvfree for larger packets.
Date: Thu, 29 Sep 2022 18:35:45 -0700 [thread overview]
Message-ID: <20220929183545.6ff5048a@kernel.org> (raw)
In-Reply-To: <CADgJSGGNjsnmzVdHkhqDN+_1cJxcPYe-U=a4A4TAL8PA6=owCw@mail.gmail.com>
On Fri, 30 Sep 2022 09:49:54 +0900 Junichi Uekawa (上川純一) wrote:
> > > I think they want it in 6.0 as it fixes a crash.
> >
> > I thought it's just an OOM leading to send failure. Junichi could you
> > repost with the tags collected and the header for that stack trace
> > included? The line that says it's just an OOM...
> >
>
> I think this is what you asked for but I don't quite know what you
> mean by the tags
We call Reviewed-by: Acked-by: Fixes: etc trailers "tags".
Don't worry tho, you shared the full stack trace now, I'll
fix the message up when applying.
next prev parent reply other threads:[~2022-09-30 1:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:45 [PATCH] vhost/vsock: Use kvmalloc/kvfree for larger packets Junichi Uekawa
2022-09-28 8:28 ` Stefano Garzarella
2022-09-28 8:28 ` Stefano Garzarella
2022-09-28 9:31 ` Michael S. Tsirkin
2022-09-28 9:31 ` Michael S. Tsirkin
2022-09-28 15:11 ` Stefano Garzarella
2022-09-28 15:11 ` Stefano Garzarella
2022-09-27 10:36 ` Bobby Eshleman
2022-09-28 20:02 ` Michael S. Tsirkin
2022-09-28 20:02 ` Michael S. Tsirkin
2022-09-29 7:40 ` Stefano Garzarella
2022-09-29 7:40 ` Stefano Garzarella
2022-09-29 7:47 ` Michael S. Tsirkin
2022-09-29 7:47 ` Michael S. Tsirkin
2022-09-28 23:14 ` Junichi Uekawa (上川純一)
2022-09-29 7:19 ` Michael S. Tsirkin
2022-09-29 7:19 ` Michael S. Tsirkin
2022-09-29 7:46 ` Stefano Garzarella
2022-09-29 7:46 ` Stefano Garzarella
2022-09-29 7:49 ` Michael S. Tsirkin
2022-09-29 7:49 ` Michael S. Tsirkin
2022-09-29 16:07 ` Jakub Kicinski
2022-09-29 16:25 ` Michael S. Tsirkin
2022-09-29 16:25 ` Michael S. Tsirkin
2022-09-29 18:07 ` Jakub Kicinski
2022-09-30 0:49 ` Junichi Uekawa (上川純一)
2022-09-30 1:35 ` Jakub Kicinski [this message]
2022-09-30 1:50 ` patchwork-bot+netdevbpf
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=20220929183545.6ff5048a@kernel.org \
--to=kuba@kernel.org \
--cc=bobby.eshleman@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=uekawa@chromium.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.