All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Zhao Heming <heming.zhao@suse.com>
Cc: linux-raid@vger.kernel.org, song@kernel.org, hch@lst.de,
	guoqing.jiang@cloud.ionos.com, lidong.zhong@suse.com,
	xni@redhat.com, neilb@suse.de, colyli@suse.com
Subject: Re: [PATCH] md: md_open returns -EBUSY when entering racing area
Date: Sat, 3 Apr 2021 18:11:58 +0200	[thread overview]
Message-ID: <20210403161158.GA4657@lst.de> (raw)
In-Reply-To: <1617418885-23423-1-git-send-email-heming.zhao@suse.com>

This defintively looks better than the ERESTARTSYS hack.

I think I'll defer the whole blkdev_get refactoring and bd_mutex to
open_mutex conversion to the next merge window, so I think we should
be fine with this plus the mddev_find split.

Reviewed-by: Christoph Hellwig <hch@lst.de>

  reply	other threads:[~2021-04-03 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  3:01 [PATCH] md: md_open returns -EBUSY when entering racing area Zhao Heming
2021-04-03 16:11 ` Christoph Hellwig [this message]
2021-04-04  2:02   ` heming.zhao

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=20210403161158.GA4657@lst.de \
    --to=hch@lst.de \
    --cc=colyli@suse.com \
    --cc=guoqing.jiang@cloud.ionos.com \
    --cc=heming.zhao@suse.com \
    --cc=lidong.zhong@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=song@kernel.org \
    --cc=xni@redhat.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.