public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Stefan Haberland <sth@linux.ibm.com>,
	Jan Hoeppner <hoeppner@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-block@vger.kernel.org
Subject: can we kill the internal blkdev_get in the dasd driver now?
Date: Mon, 8 Mar 2021 08:49:31 +0100	[thread overview]
Message-ID: <YEXXCw2MYKzAIKX6@infradead.org> (raw)

Hi DASD maintainers,

I've recently changed the life time rules for struct block_device so
that is is a long-living instead of an ephemeral structure, that is the
whole device block_device exists from the time the disk is alloced until
it is feed, and the partitions exist from as soon as they are scanned.

With this the blkdev_get in the DASD driver should not be required, but
there seems to be a lot of magic that accounts of it in the open count.

Any chance one of you maintainers could try to remove it to further
simplify our open and liftetime rules?


             reply	other threads:[~2021-03-08  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08  7:49 Christoph Hellwig [this message]
2021-03-08  8:45 ` can we kill the internal blkdev_get in the dasd driver now? Stefan Haberland

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=YEXXCw2MYKzAIKX6@infradead.org \
    --to=hch@infradead.org \
    --cc=hoeppner@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sth@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox