All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <frezidok1@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: <martin.jansa@gmail.com>
Subject: Re: [OE-core] [PATCH] io_uring-writev: open output file through io_uring
Date: Tue, 01 Sep 2026 07:34:58 +0200	[thread overview]
Message-ID: <DL3QHRJANNVL.8YPDPUMNTLHZ@bootlin.com> (raw)
In-Reply-To: <20260831080223.124050-1-frezidok1@gmail.com>

On Mon Aug 31, 2026 at 10:02 AM CEST, Dmitry Sakhonchik via lists.openembedded.org wrote:
> From: Dmitry Sakhonchik <frezidok1@gmail.com>
>
> The existing test creates the output file with open(), which ends up
> using openat() and is therefore intercepted by pseudo before the actual
> io_uring write operation happens.
>
> Use IORING_OP_OPENAT to create the output file through io_uring as well.
> This makes the test successfully bypass pseudo
>
> io-uring-writev.bb: wrynose doesn't support "S = ${WORKDIR}" anymore, fix it
>
> [YOCTO #15244]
>
> Signed-off-by: Dmitry Sakhonchik <frezidok1@gmail.com>
> ---

Hi Dmitry,

I suspect this was targeting Martin's branch and not master? Otherwise
we are missing the commits adding the io-uring-writev recipes.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-09-01  5:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  8:02 [PATCH] io_uring-writev: open output file through io_uring frezidok1
2026-09-01  5:34 ` Mathieu Dubois-Briand [this message]
2026-09-01  5:48   ` [OE-core] " Dmitry Sakhonchik

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=DL3QHRJANNVL.8YPDPUMNTLHZ@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=frezidok1@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.