From: Cyril Hrubis <chrubis@suse.cz>
To: xiao shoukui <xiaoshoukui@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1 1/1] Add ioctl_loop08 test for LOOP_GET_STATUS lock imbalance
Date: Fri, 10 Feb 2023 13:13:45 +0100 [thread overview]
Message-ID: <Y+Y0+ajVAD3JaBQv@yuki> (raw)
In-Reply-To: <CAOHshYVJDij+fqanWw+XMod-LWa0tqvJDZWXPqhSZxcBSHH8mA@mail.gmail.com>
Hi!
> Sincere thanks for your advice.
> Based on my tests，the lockdep will block the ioctl request thread return to
> userspace when it detect a lock imbalance. Place ioctl request in the main
> thread, there is no chance to execute find_kmsg for determining what
> exactly a lock problem happaned and printing the test result.
Hmm, then maybe it would be easier and more reliable to run the ioctl()
in a child processes and fail the test when the parent detects the
child to lockup.
I suppose that the process that called the ioctl() ends up in the D
state, right? In that case the parent read the /proc/pid/stat a few
times with slight delays between them and if the process keeps hanging
in D state we declare it blocked forever.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-02-10 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 8:44 [LTP] [PATCH 1/1 1/1] Add ioctl_loop08 test for LOOP_GET_STATUS lock imbalance xiaoshoukui
2023-02-10 10:46 ` Cyril Hrubis
2023-02-10 11:42 ` xiao shoukui
2023-02-10 12:13 ` Cyril Hrubis [this message]
2023-02-13 9:35 ` xiao shoukui
2023-02-14 9:55 ` Richard Palethorpe
-- strict thread matches above, loose matches on Subject: below --
2023-02-10 8:05 xiaoshoukui
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=Y+Y0+ajVAD3JaBQv@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xiaoshoukui@gmail.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.