From: Nicolas Schichan <nschichan@freebox.fr>
To: Neil Brown <neilb@suse.de>, LKML <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org
Subject: livelock during MD device open
Date: Tue, 14 Jan 2014 18:14:46 +0100 [thread overview]
Message-ID: <52D57086.1000508@freebox.fr> (raw)
Hi,
I have recently been trying to find the cause a livelock occurring during MD
device open.
The livelock happens when a process tries to open an MD device for the
first time and another opens the same MD device and sends an invalid
ioctl:
Process 1 Process 2
--------- ---------
md_alloc()
mddev_find()
-> returns a new mddev with
hold_active == UNTIL_IOCTL
add_disk()
-> sends KOBJ_ADD uevent
(sees KOBJ_ADD uevent for device)
md_open()
md_ioctl(INVALID_IOCTL)
-> returns ENODEV and clears
mddev->hold_active
md_release()
md_put()
-> deletes the mddev as
hold_active is 0
md_open()
mddev_find()
-> returns a newly
allocated mddev with
mddev->gendisk == NULL
-> returns with ERESTARTSYS
(kernel restarts the open syscall)
As to how to fix this, I see two possibilities:
- don't set hold_active to 0 if err is -ENODEV in the abort_unlock
path in md_ioctl().
- check cmd parameter early in md_ioctl() and return -ENOTTY if the
cmd parameter is not a valid MD ioctl.
Please advise on the preferred way to fix this, I'll be glad to send a
patch for whatever is the preferred solution.
I have also a simple C program that I can send should you want to reproduce
the issue.
Regards,
--
Nicolas Schichan
Freebox SAS
next reply other threads:[~2014-01-14 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 17:14 Nicolas Schichan [this message]
2014-01-15 1:57 ` livelock during MD device open NeilBrown
2014-01-15 13:11 ` Nicolas Schichan
2014-01-15 15:58 ` [PATCH] md: check command validity early in md_ioctl() Nicolas Schichan
2014-01-15 21:55 ` NeilBrown
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=52D57086.1000508@freebox.fr \
--to=nschichan@freebox.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.