From: Jens Axboe <axboe@kernel.dk>
To: Stefan Metzmacher <metze@samba.org>
Cc: io-uring <io-uring@vger.kernel.org>,
Samba Technical <samba-technical@lists.samba.org>,
Jeremy Allison <jra@samba.org>
Subject: Re: Data Corruption bug with Samba's vfs_iouring and Linux 5.6.7/5.7rc3
Date: Tue, 5 May 2020 08:41:10 -0600 [thread overview]
Message-ID: <102c824b-b2f5-bbb1-02da-d2a78c3ff460@kernel.dk> (raw)
In-Reply-To: <0009f6b7-9139-35c7-c0b1-b29df2a67f70@samba.org>
On 5/5/20 4:04 AM, Stefan Metzmacher wrote:
> Hi Jens,
>
> we currently have a bug report [1][2] regarding a data corruption with
> Samba's vfs_io_uring.c [3].
>
> Is there're a know problem in newer kernels? It seems the 5.3 Kernel
> doesn't have the problem (at least Jeremy wasn't able to reproduce it
> on the Ubuntu 5.3 kernel).
>
> Do you have any hints how to track that down?
I'll take a look at this! Any chance Jeremy can try 5.4 and 5.5 as well,
just to see where we're at, roughly? That might be very helpful.
--
Jens Axboe
next prev parent reply other threads:[~2020-05-05 14:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 10:04 Data Corruption bug with Samba's vfs_iouring and Linux 5.6.7/5.7rc3 Stefan Metzmacher
2020-05-05 14:41 ` Jens Axboe [this message]
2020-05-05 15:44 ` Jens Axboe
2020-05-05 16:53 ` Jens Axboe
2020-05-05 17:39 ` Jens Axboe
2020-05-05 17:48 ` Jeremy Allison
2020-05-05 17:50 ` Jens Axboe
[not found] ` <3a3e311c7a4bc4d4df371b95ca0c66a792fab986.camel@cryptolab.net>
2020-05-06 10:33 ` Stefan Metzmacher
2020-05-06 10:41 ` Stefan Metzmacher
[not found] ` <62e94d8a6cecf60cfba7e5ca083e90bc8f216d61.camel@cryptolab.net>
2020-05-06 14:08 ` Stefan Metzmacher
2020-05-06 14:43 ` Andreas Schneider
2020-05-06 14:46 ` Andreas Schneider
2020-05-06 15:06 ` Stefan Metzmacher
2020-05-06 17:03 ` Jeremy Allison
2020-05-06 17:13 ` Jeremy Allison
2020-05-06 18:01 ` Jeremy Allison
2020-05-05 20:19 ` Stefan Metzmacher
2020-05-06 12:55 ` Pavel Begunkov
2020-05-06 15:20 ` Stefan Metzmacher
2020-05-06 15:42 ` Pavel Begunkov
2020-05-07 16:43 ` Jens Axboe
2020-05-07 16:48 ` Jeremy Allison
2020-05-07 16:50 ` Jens Axboe
2020-05-07 18:31 ` Jeremy Allison
2020-05-07 18:35 ` Jens Axboe
2020-05-07 18:55 ` Jeremy Allison
2020-05-07 18:58 ` Jens Axboe
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=102c824b-b2f5-bbb1-02da-d2a78c3ff460@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=jra@samba.org \
--cc=metze@samba.org \
--cc=samba-technical@lists.samba.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.