All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Heming Zhao <heming.zhao@suse.com>,
	Joseph Qi <joseph.qi@linux.alibaba.com>,
	ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] report BUG: io_uring triggers umount error
Date: Fri, 24 Feb 2023 18:59:47 +0800	[thread overview]
Message-ID: <e1fc4970-010f-17a5-c2b3-7bf2dc937e73@gmail.com> (raw)
In-Reply-To: <87be76c0-b94a-d6e6-3435-e1764110302a@suse.com>



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 2/24/23 2:54 PM, Joseph Qi wrote:
>>>> I can reproduce this in my local VM.
>>>> I've traced ocfs2_dismount_volume and found that it hasn't been called.
>>>> So EBUSY is returned in VFS layer. I guess something wrong when doing
>>>> a copy with linked SQEs (normal copy seems no problem).
>>>>
>>>
>>> I am inclined to agree with you. I also test liburing examples apps
>>> on ext4 partition, everything looks fine.
>>>
>>> I used below bpftrace method, the retval is '3'.
>>>   bpftrace -e 'kr:mnt_get_count{printf("%d\n", retval);}'
>>>
>>> It responds to flow: path_umount() => do_umount => mnt_get_count (gets '3')
>>>
>> Yes, that's the place return EBUSY.
>> So the problem seems to be getmnt/putmnt not match in this case.
>>
> 
> I didn't familiar with setting up kernel bi-search env. I used one last year
> openSUSE tumblweed (with kernel 5.16.2), this umount issue doesn't exist.
> So there is a possibility one ocfs2 commit introduced this issue.
>You can checkout each mailine version like Linux 6.0, 6.1, ... and try
to check if it can be reproduced.

I've tried trace mntget/mntput using the following bpftrace script,
link-cp output shows it misses a fput.

#include <linux/mount.h>
#include <linux/string.h>

kprobe:mntget
{
	$n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name;

	if (!strncmp(str($n), "ocfs2", 5)) {
		@[comm] += 1;

		printf("%s", kstack);
	}
}

kprobe:mntput
{
	$n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name;

	if (!strncmp(str($n), "ocfs2", 5)) {
		@[comm] +=1;

		printf("%s", kstack);
	}
}

Joseph

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

  reply	other threads:[~2023-02-24 11:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  0:32 [Ocfs2-devel] report BUG: io_uring triggers umount error Heming Zhao via Ocfs2-devel
2023-02-24  6:54 ` 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 [this message]
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=e1fc4970-010f-17a5-c2b3-7bf2dc937e73@gmail.com \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=heming.zhao@suse.com \
    --cc=jiangqi903@gmail.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.