All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Jens Axboe <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2] bdev: Refresh bdev size for disks without partitioning
Date: Mon, 21 Oct 2019 10:37:58 +0200	[thread overview]
Message-ID: <20191021083132.5351-1-jack@suse.cz> (raw)

Hello,

I've been debugging for quite a long time strange issues with encrypted DVDs
not being readable on Linux (bko#194965). In the end I've tracked down the
problem to the fact that block device size is not updated when the media is
inserted in case the DVD device is already open. This is IMO a bug in block
device code as the size gets properly update in case the device has partition
scanning enabled.  The following series fixes the problem by refreshing disk
size on each open even for devices with partition scanning disabled.

								Honza

             reply	other threads:[~2019-10-21  8:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  8:37 Jan Kara [this message]
2019-10-21  8:37 ` [PATCH 1/2] bdev: Factor out bdev revalidation into a common helper Jan Kara
2019-10-22  7:58   ` Damien Le Moal
2019-10-22  9:15     ` Jan Kara
2019-10-22  9:31       ` Damien Le Moal
2019-10-21  8:38 ` [PATCH 2/2] bdev: Refresh bdev size for disks without partitioning Jan Kara
2019-10-21  8:49   ` Guoqing Jiang
2019-10-21  9:12     ` Jan Kara
2019-10-21  9:27       ` Guoqing Jiang
2019-10-21  9:36         ` Johannes Thumshirn
2019-10-21  9:38           ` Guoqing Jiang
2019-10-21  9:40         ` Jan Kara
2019-10-21  9:43           ` Guoqing Jiang
2019-11-03 14:53 ` [PATCH 0/2] " Jens Axboe
2019-11-04  8:08   ` Jan Kara
2019-11-04 23:48     ` Christoph Hellwig
2019-11-05  8:59       ` Jan Kara

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=20191021083132.5351-1-jack@suse.cz \
    --to=jack@suse.cz \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    /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.