Re: ramdisk corruption problems - was: RE: pivot_root and initrd kern el panic woes

[Andrea Arcangeli]

On Thu, Dec 20, 2001 at 11:46:23AM -0800, Linus Torvalds wrote:
> In article <[e-mail]> you write:
> >Yes, this does fix the problem.  Thank you very much!
> >
> >Hopefully something like this will make it into 2.4.18?
> 
> This does not seem quite right.
> 
> >Tachino Nobuhiro ([e-mail]) wrote:
> >> Hello,
> >> 
> >> Following patch may fix your problem. 
> >> 
> >> diff -r -u linux-2.4.17-rc2.org/drivers/block/rd.c 
> >> linux-2.4.17-rc2/drivers/block/rd.c
> >> --- linux-2.4.17-rc2.org/drivers/block/rd.c	Thu Dec 20 20:30:57 2001
> >> +++ linux-2.4.17-rc2/drivers/block/rd.c	Thu Dec 20 20:46:53 2001
> >> @@ -194,9 +194,11 @@
> >>  static int ramdisk_readpage(struct file *file, struct page * page)
> >>  {
> >>  	if (!Page_Uptodate(page)) {
> >> -		memset(kmap(page), 0, PAGE_CACHE_SIZE);
> >> -		kunmap(page);
> >> -		flush_dcache_page(page);
> >> +		if (!page->buffers) {
> >> +			memset(kmap(page), 0, PAGE_CACHE_SIZE);
> >> +			kunmap(page);
> >> +			flush_dcache_page(page);
> >> +		}
> >>  		SetPageUptodate(page);
> >>  	}
> >>  	UnlockPage(page);
> >> 
> >> 
> >>   grow_dev_page() creates not Uptodate page which has valid 
> >> buffers, so
> >> it is wrong that ramdisk_readpage() clears whole page unconditionally.
> 
> The problem is that having buffers doesn't necessarily always mean that
> they are valid, nor that _all_ of them are valid.
> 
> Also, if the ramdisk "readpage" code is wrong, then so is the
> "prepare_write" code.  They share the same logic, which basically says
> that "if the page isn't up-to-date, then it is zero".  Which is always
> true for normal read/write accesses, but as you found out it's not true
> when parts of the page have been accessed by filesystems through the
> buffers. 

subtle, while writing and testing that code the buffercache was not
sharing the physical address space yet, so it was stable, then it kept to
work somehow till today because only metadata writes into holes would
trigger it.

> 
> So the code _should_ use a common helper, something like
> 
> 	static void ramdisk_updatepage(struct page * page)
> 	{
> 		if (!Page_Uptodate(page)) {
> 			struct buffer_head *bh = page->buffers;
> 			void * address = page_address(page);
> 			if (bh) {
> 				struct buffer_head *tmp = bh;
> 				do {
> 					if (!buffer_uptodate(tmp)) {
> 						memset(address, 0, tmp->b_size);
> 						 set_buffer_uptodate(tmp);
> 					}
> 					address += tmp->b_size;
> 					tmp = tmp->b_this_page;
> 				} while (tmp != bh);
> 			} else
> 				memset(address, 0, PAGE_SIZE);
> 			flush_dcache_page(page);
> 			SetPageUptodate(page);
> 		}
> 	}
> 
> and then ramdisk_readpage() would just be
> 
> 	kmap(page);
> 	ramdisk_updatepage(page);
> 	UnlockPage(page);
> 	kunmap(page);
> 	return 0;
> 
> while ramdisk_prepare_write() would be
> 
> 	ramdisk_updatepage(page);
> 	SetPageDirty(page);
> 	return 0;

agreed. rd_blkdev_pagecache_IO will as well do:

			err = 0;

			kmap(page);
			ramdisk_updatepage(page);
			kunmap(page);

			unlock = 1;

Andrea