similar to: [PATCH V3] io_uring: fix IO hang in io_wq_put_and_exit from do_exit()

Heming reported a BUG when using io_uring doing link-cp on ocfs2. [1] Do the following steps can reproduce this BUG: mount -t ocfs2 /dev/vdc /mnt/ocfs2 cp testfile /mnt/ocfs2/ ./link-cp /mnt/ocfs2/testfile /mnt/ocfs2/testfile.1 umount /mnt/ocfs2 Then umount will fail, and it outputs: umount: /mnt/ocfs2: target is busy. While tracing umount, it blames mnt_get_count() not return as expected. Do a

Hello, Using Samba 4.12.1 with kernel 5.6.7 on Gentoo Linux, I wanted to test the new vfs_io_uring module. * Stand-alone Samba server acting as NAS for home setup. * /media/usb-backup is a mounted read-only btrfs filesystem. * Samba share exported as: ===== smb.conf ===== [global] ??? log level = 1 ??? workgroup = WORKGROUP ??? netbios name = NAS ??? server string = Samba Server ???

On 01/05/2020 14:35, A L via samba wrote: > True.. I just copied from another share. Would that have a impact on > the current problem with io_uring? I do not know, I'll leave that up to Jeremy, but it has to be worth trying without the lines. Rowland

On Wed, Apr 19, 2023 at 09:45:06AM -0700, Jakub Kicinski wrote: > > Can you explain what the actual use case is? > > > > From the original patchset I suspect it is dma mapping something very > > long term and then maybe doing syncs on it as needed? > > In this case yes, pinned user memory, it gets sliced up into MTU sized > chunks, fed into an Rx queue of a

On Fri, May 01, 2020 at 05:07:17PM +0200, A L via samba wrote: > > On 2020-05-01 15:59, Rowland penny via samba wrote: > > On 01/05/2020 14:35, A L via samba wrote: > > > True.. I just copied from another share. Would that have a impact on > > > the current problem with io_uring? > > > > I do not know, I'll leave that up to Jeremy, but it has to be

On 2020-04-27 18:45, Jeremy Allison via samba wrote: > On Mon, Apr 27, 2020 at 10:27:17AM +0200, A L via samba wrote: >> On 2020-04-26 19:46, Jeremy Allison via samba wrote: >>> On Sun, Apr 26, 2020 at 11:51:42AM +0200, A L via samba wrote: >>>> * Connected from a Windows 10 computer over 1G ethernet. * Copy >>>> data using Windows Explorer and

Hi, On 2/27/23 10:59 AM, Joseph Qi via Ocfs2-devel wrote: > > > On 2/26/23 11:22 PM, Heming Zhao wrote: >> On Sun, Feb 26, 2023 at 04:45:44PM +0800, Heming Zhao via Ocfs2-devel wrote: >>> On Fri, Feb 24, 2023 at 06:59:47PM +0800, Joseph Qi wrote: >>>> >>>> >>>> On 2/24/23 4:03 PM, Heming Zhao wrote: >>>>> On 2/24/23 3:52

On 2/26/23 11:22 PM, Heming Zhao wrote: > On Sun, Feb 26, 2023 at 04:45:44PM +0800, Heming Zhao via Ocfs2-devel wrote: >> On Fri, Feb 24, 2023 at 06:59:47PM +0800, Joseph Qi wrote: >>> >>> >>> On 2/24/23 4:03 PM, Heming Zhao wrote: >>>> On 2/24/23 3:52 PM, Joseph Qi wrote: >>>>> >>>>> >>>>> On 2/24/23 3:48

On Fri, May 01, 2020 at 09:27:58PM +0200, A L via samba wrote: > > Jeremy. > I did not use a command line, but rather File Explorer > 1) In File explorer, go to \\SAMBA\share_io_uring\ > 2) Select folder "test2-ro" and choose copy > 3) Paste to a local drive > > The amount of files not working seems to vary, but usually within the 10 > first copied files. You

On Sun, Feb 26, 2023 at 04:45:44PM +0800, Heming Zhao via Ocfs2-devel wrote: > On Fri, Feb 24, 2023 at 06:59:47PM +0800, Joseph Qi wrote: > > > > > > On 2/24/23 4:03 PM, Heming Zhao wrote: > > > On 2/24/23 3:52 PM, Joseph Qi wrote: > > >> > > >> > > >> On 2/24/23 3:48 PM, Heming Zhao via Ocfs2-devel wrote: > > >>> On

On 2020-05-01 22:04, Jeremy Allison via samba wrote: > On Fri, May 01, 2020 at 09:27:58PM +0200, A L via samba wrote: >>> Jeremy. >> I did not use a command line, but rather File Explorer >> 1) In File explorer, go to \\SAMBA\share_io_uring\ >> 2) Select folder "test2-ro" and choose copy >> 3) Paste to a local drive >> >> The amount of

On Sat, May 02, 2020 at 11:34:41AM +0200, A L wrote: > ######## > I also tried various combinations of io_uring settings. > > io_uring:sqpoll = true/false > io_uring:num_entries = 2, 4, 8, 64, 128 (default), 256 > > Between each test i do "echo 3 > /proc/sys/vm/drop_caches" and restart the > samba service. > > One difference I noticed is that there is

On Thu, Jul 23, 2020 at 11:32:39AM +0100, Stefan Hajnoczi wrote: > On Thu, Jul 16, 2020 at 11:33:44AM +0200, Stefano Garzarella wrote: > > +Cc Michael, Stefan, virtualization at lists.linux-foundation.org > > > > On Thu, Jul 16, 2020 at 09:06:14AM +0100, Richard W.M. Jones wrote: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1857515 > > >

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API. Changes since v1: - drop a few patches - fix a comment typo - cover the newly merged use_mm/unuse_mm caller in vfio

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API. Changes since v1: - drop a few patches - fix a comment typo - cover the newly merged use_mm/unuse_mm caller in vfio

Some architectures like arm64 and s390 require USER_DS to be set for kernel threads to access user address space, which is the whole purpose of kthread_use_mm, but other like x86 don't. That has lead to a huge mess where some callers are fixed up once they are tested on said architectures, while others linger around and yet other like io_uring try to do "clever" optimizations for

Some architectures like arm64 and s390 require USER_DS to be set for kernel threads to access user address space, which is the whole purpose of kthread_use_mm, but other like x86 don't. That has lead to a huge mess where some callers are fixed up once they are tested on said architectures, while others linger around and yet other like io_uring try to do "clever" optimizations for

On Thu, Apr 30, 2020 at 10:25:49AM +0200, A L wrote: > So I did some more tests. smbclient mget does not copy in the same way > Windows Explorer does. When copying in Windows Explorer, there are many > multiple concurrent threads used to transfer the files. With smbclient mget > there are no corruptions, both locally and over the network from another > Linux machine. > > I