public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [PATCH v4 1/6] io_uring/mock: add basic infra for test mock files
Date: Fri, 30 May 2025 15:09:35 +0100	[thread overview]
Message-ID: <eb81c562-7030-48e0-85de-6192f3f5845a@gmail.com> (raw)
In-Reply-To: <cf2e4b4b-c229-408d-ac86-ab259a87e90e@kernel.dk>

On 5/30/25 14:28, Jens Axboe wrote:
> On 5/30/25 6:51 AM, Pavel Begunkov wrote:
>> diff --git a/init/Kconfig b/init/Kconfig
>> index 63f5974b9fa6..9e8a5b810804 100644
>> --- a/init/Kconfig
>> +++ b/init/Kconfig
>> @@ -1774,6 +1774,17 @@ config GCOV_PROFILE_URING
>>   	  the io_uring subsystem, hence this should only be enabled for
>>   	  specific test purposes.
>>   
>> +config IO_URING_MOCK_FILE
>> +	tristate "Enable io_uring mock files (Experimental)" if EXPERT
>> +	default n
>> +	depends on IO_URING && KASAN
>> +	help
>> +	  Enable mock files for io_uring subststem testing. The ABI might
>> +	  still change, so it's still experimental and should only be enabled
>> +	  for specific test purposes.
>> +
>> +	  If unsure, say N.
> 
> As mentioned in the other email, I don't think we should include KASAN
> here.

I disagree. It's supposed to give a superset of coverage, if not,
mocking should be improved. It might be seen as a nuisance that you
can't run it with a stock kernel, but that desire is already half
step from "let's enable it for prod kernels for testing", and then
distributions will start forcing it on, because as you said "People
do all sorts of weird stuff".

-- 
Pavel Begunkov


  parent reply	other threads:[~2025-05-30 14:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-30 12:51 [PATCH v4 0/6] io_uring/mock: add basic infra for test mock files Pavel Begunkov
2025-05-30 12:51 ` [PATCH v4 1/6] " Pavel Begunkov
2025-05-30 13:28   ` Jens Axboe
2025-05-30 13:57     ` Pavel Begunkov
2025-05-30 14:36       ` Jens Axboe
2025-05-30 14:09     ` Pavel Begunkov [this message]
2025-05-30 14:12       ` Pavel Begunkov
2025-05-30 14:26         ` Pavel Begunkov
2025-05-30 14:41           ` Jens Axboe
2025-05-30 15:11             ` Pavel Begunkov
2025-05-30 15:30               ` Jens Axboe
2025-05-30 18:14                 ` Pavel Begunkov
2025-06-02 15:19                   ` Jens Axboe
2025-06-02 15:31                     ` Pavel Begunkov
2025-06-02 15:41                       ` Jens Axboe
2025-05-30 18:04   ` Keith Busch
2025-05-30 18:21     ` Pavel Begunkov
2025-06-02 13:44       ` Jens Axboe
2025-05-30 12:51 ` [PATCH v4 2/6] io_uring/mock: add cmd using vectored regbufs Pavel Begunkov
2025-05-30 13:25   ` Jens Axboe
2025-05-30 13:40     ` Pavel Begunkov
2025-05-30 14:37       ` Jens Axboe
2025-05-30 14:53         ` Pavel Begunkov
2025-05-30 15:34           ` Jens Axboe
2025-05-30 12:52 ` [PATCH v4 3/6] io_uring/mock: add sync read/write Pavel Begunkov
2025-05-30 12:52 ` [PATCH v4 4/6] io_uring/mock: allow to choose FMODE_NOWAIT Pavel Begunkov
2025-05-30 12:52 ` [PATCH v4 5/6] io_uring/mock: support for async read/write Pavel Begunkov
2025-05-30 13:27   ` Jens Axboe
2025-05-30 13:49     ` Pavel Begunkov
2025-05-30 14:38       ` Jens Axboe
2025-05-30 12:52 ` [PATCH v4 6/6] io_uring/mock: add trivial poll handler Pavel Begunkov

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=eb81c562-7030-48e0-85de-6192f3f5845a@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.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