public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Roman Kiryanov <rkir@google.com>
Cc: virtio-dev@lists.linux.dev, JP Cottin <jpcottin@google.com>
Subject: Re: VIRTIO_VSOCK_OP_REQUEST with the same src_port from a guest
Date: Mon, 1 Jul 2024 17:01:14 -0400	[thread overview]
Message-ID: <20240701165704-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAOGAQerR1Y59gXq=PVSPtWMrDbxZWfA_T1GcOFSOqP09k7Mwuw@mail.gmail.com>

On Mon, Jul 01, 2024 at 12:55:46PM -0700, Roman Kiryanov wrote:
> On Mon, Jul 1, 2024 at 12:40 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> > Can Linux driver ever trigger this? Some other driver?
> 
> I have never seen a driver with this behavior so far.
> 
> > If this is something that drivers don't actually ever
> > trigger, why does it matter how exactly the device
> > behaves?
> 
> I think there is a value in having the spec to cover all cases.

Well we don't really do it for other devices.
We focus on how things fail when it's important e.g. for security.

Basically spec has been out there for a while and we can't
declare existing devices non-compliant.
We can add a recommendation.
Given no driver actually does this, the value seems low.

-- 
MST


      reply	other threads:[~2024-07-01 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 17:35 VIRTIO_VSOCK_OP_REQUEST with the same src_port from a guest Roman Kiryanov
2024-07-01 18:44 ` Michael S. Tsirkin
2024-07-01 19:16   ` Roman Kiryanov
2024-07-01 19:40     ` Michael S. Tsirkin
2024-07-01 19:55       ` Roman Kiryanov
2024-07-01 21:01         ` Michael S. Tsirkin [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=20240701165704-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jpcottin@google.com \
    --cc=rkir@google.com \
    --cc=virtio-dev@lists.linux.dev \
    /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