Re: ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem?

From: Andrew Morton (
Date: Wed Jun 11 2003 - 19:29:58 EST

Andy Pfiffer <> wrote:
> So now the important question: is it wrong to not sync_blockdev() until
> the count drops to 0?

Should be OK. The close will not sync anything if someone else has the
blockdev open (ie: there's a filesystem mounted there).

But sync() should certainly write everything out, and lilo does perform a

I'd be interested in seeing the contents of /proc/meminfo immediately after
the lilo run, see if there's any dirty memory left around.

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

This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:30 EST