All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heming Zhao via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: joseph.qi@linux.alibaba.com, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] report BUG: io_uring triggers umount error
Date: Fri, 24 Feb 2023 08:32:51 +0800	[thread overview]
Message-ID: <20230224003251.otqzmap2f64o3fpf@c73> (raw)

Hello List,

I found a weird bug on ocfs2. I am busying with other jobs, if anyone have time
he/she could fix it. This bug is blocking fstest generic/013 test case, and also
blocking fstest to do later test cases.

How to trigger:
```
git clone git://git.kernel.dk/liburing.git
cd liburing
make
cd examples
mount -t ocfs2 /dev/sda /mnt
cp /etc/hosts /mnt/a
./link-cp /mnt/a /mnt/b
umount /mnt
```

umount trigger error message:
```
# umount /mnt 
umount: /mnt: target is busy.
```

The umount error can only be triggered by liburing write operation.

Thanks,
Heming

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

             reply	other threads:[~2023-02-24  0:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  0:32 Heming Zhao via Ocfs2-devel [this message]
2023-02-24  6:54 ` [Ocfs2-devel] report BUG: io_uring triggers umount error Joseph Qi via Ocfs2-devel
2023-02-24  7:48   ` Heming Zhao via Ocfs2-devel
2023-02-24  7:52     ` Joseph Qi via Ocfs2-devel
2023-02-24  8:03       ` Heming Zhao via Ocfs2-devel
2023-02-24 10:59         ` Joseph Qi via Ocfs2-devel
2023-02-26  8:45           ` Heming Zhao via Ocfs2-devel
2023-02-26 15:22             ` Heming Zhao via Ocfs2-devel
2023-02-27  2:59               ` Joseph Qi via Ocfs2-devel
2023-02-28  4:50                 ` Joseph Qi via Ocfs2-devel
2023-03-01  2:06                 ` Joseph Qi via Ocfs2-devel
2023-03-01  9:49                   ` Heming Zhao via Ocfs2-devel

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=20230224003251.otqzmap2f64o3fpf@c73 \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=heming.zhao@suse.com \
    --cc=joseph.qi@linux.alibaba.com \
    /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.