On 8/27/20 1:47 AM, Christoph Hellwig wrote:
> Jens, can you consider this for 5.9? It reliably fixes the reported
> hangs with nvme hotremoval that we've had for a few releases.
I've queued this up for 5.10. I think it's too late for 5.9 at this
point, and it's not a regression in this release.
Jens, can you consider this for 5.9? It reliably fixes the reported
hangs with nvme hotremoval that we've had for a few releases.
On Sun, Aug 23, 2020 at 11:10:40AM +0200, Christoph Hellwig wrote:
> Hi Jens,
>
> this series fixes how we update i_size for the block device inodes (and
> thus the b
Hi Jens,
this series fixes how we update i_size for the block device inodes (and
thus the block device). Different helpers use two different locks
(bd_mutex and i_rwsem) to protect the update, and it appears device
mapper uses yet another internal lock. A lot of the drivers do the
update handcra
Hi Jens,
this series fixes how we update i_size for the block device inodes (and
thus the block device). Different helpers use two different locks
(bd_mutex and i_rwsem) to protect the update, and it appears device
mapper uses yet another internal lock. A lot of the drivers do the
update handcra
3.17-stable review patch. If anyone has any objections, please let me know.
--
From: Ezequiel Garcia
commit 978d6496758d19de2431ebf163337fc7b92f8c45 upstream.
We are currently taking the block device size from the ubi_volume_info.size
field. However, this is not the amount of
problems are:
- losetup set up the device in two ioctl:
LOOP_SET_FD and LOOP_SET_STATUS64.
- LOOP_SET_STATUS64 only update size of gendisk.
Block device size will be updated lazily when device comes to use. If udev
rushes in between the two ioctl, it will bring
On 2012-12-04 13:13, Meelis Roos wrote:
>> Most likely Linus' shuffle of code in there. For ease of debugging, can
>> you a bisect of fs/ between rc7 and rc8? Just do;
>
> Already found the discussion and patch in 3.7-rc8 thread. Linus's patch
> worked fine for me too.
Even better! Thanks.
--
> Most likely Linus' shuffle of code in there. For ease of debugging, can
> you a bisect of fs/ between rc7 and rc8? Just do;
Already found the discussion and patch in 3.7-rc8 thread. Linus's patch
worked fine for me too.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send th
On 2012-12-04 10:40, Meelis Roos wrote:
> This is on a couple of different Sun sparc64 machines with pata_ali IDE
> controller. These machines work with no warnings in 3.7-rc7 and the same
> userspace. On 3.7-rc8, I get warning about trying to access beyond end
> of device:
>
> [ 65.219323] s
This is on a couple of different Sun sparc64 machines with pata_ali IDE
controller. These machines work with no warnings in 3.7-rc7 and the same
userspace. On 3.7-rc8, I get warning about trying to access beyond end
of device:
[ 65.219323] scsi0 : pata_ali
[ 65.258060] scsi1 : pata_ali
[
As a response to myself, I've found it:
superblock->s_bdev->bd_inode->i_size
:)
Jan Engelhardt
--
No TOFU for me, please.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.or
Hello list,
how can I found out the size of the underlying block device when I am in
somefs_fill_super()?
Jan Engelhardt
--
No TOFU for me, please.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
12 matches
Mail list logo
