[lkml]   [2002]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: initrd and BLKFLSBUF
    amazing that people start adding complications (all that "bdev" filesystem
    stuff in recent kernels) without first getting the basics right -- the
    bd_openers accounting doesn't seem to be correct.

    On Tue, 26 Mar 2002, Tigran Aivazian wrote:

    > Hello,
    > Is blockdev --flushbufs supposed to work on /dev/ram0 if it was loaded as
    > initrd ramdisk? I unmount it and try to free the memory but hit this
    > EBUSY in drivers/block/rd.c:rd_ioctl():
    > /* special: we want to release the ramdisk memory,
    > it's not like with the other blockdevices where
    > this ioctl only flushes away the buffer cache. */
    > if ((atomic_read(&inode->i_bdev->bd_openers) > 2))
    > return -EBUSY;
    > The kernel is 2.4.9 but this code is almost the same in 2.4.18. So, who is
    > this opener that keeps the inode->i_bdev->bd_openers too high?
    > Regards,
    > Tigran

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:25    [W:0.024 / U:13.232 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site