mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Koichiro Den <den@valinux.co.jp>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/privcmd: Only claim ioreqs matching an ioeventfd
Date: Thu, 8 Oct 2026 12:37:02 +0200	[thread overview]
Message-ID: <576bbb3d-48a3-436c-b626-b0f2dd493a9e@suse.com> (raw)
In-Reply-To: <20260821084112.2374949-1-den@valinux.co.jp>


[-- Attachment #1.1.1: Type: text/plain, Size: 993 bytes --]

On 21.08.26 10:41, Koichiro Den wrote:
> The ioeventfd handler shares its event channel with the userspace device
> model. It must only claim requests that match a registered ioeventfd.
> Other requests are left for userspace.
> 
> ioeventfd_interrupt() currently marks every MMIO write INPROCESS before
> looking for a match. For an unmatched request it drops the lock and
> restores READY. Userspace may see INPROCESS and skip it. Restoring READY
> does not send another notification. If userspace handles the request at
> the same time, the READY store may overwrite its state.
> 
> Find a matching ioeventfd before changing the request state.
> 
> The lock now protects only the ioeventfd list. Use explicit virt_*mb()
> barriers for the ioreq shared with Xen.
> 
> Fixes: f0d7db7b3324 ("xen: privcmd: Add support for ioeventfd")
> Cc: stable@vger.kernel.org
> Signed-off-by: Koichiro Den <den@valinux.co.jp>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

      reply	other threads:[~2026-10-08 10:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  8:41 Koichiro Den
2026-10-08 10:37 ` Juergen Gross [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=576bbb3d-48a3-436c-b626-b0f2dd493a9e@suse.com \
    --to=jgross@suse.com \
    --cc=den@valinux.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=xen-devel@lists.xenproject.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

all inboxes | Powered by JetHome®