linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Memory Management <linux-mm@kvack.org>,
	Neil Brown <neilb@suse.de>, Anton Altaparmakov <aia21@cam.ac.uk>,
	Chris Mason <chris.mason@oracle.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 6/6] mm: fix pagecache write deadlocks
Date: Sat, 14 Oct 2006 06:19:28 +0200	[thread overview]
Message-ID: <20061014041927.GA14467@wotan.suse.de> (raw)
In-Reply-To: <20061013151457.81bb7f03.akpm@osdl.org>

On Fri, Oct 13, 2006 at 03:14:57PM -0700, Andrew Morton wrote:
> On Fri, 13 Oct 2006 18:44:52 +0200 (CEST)
> Nick Piggin <npiggin@suse.de> wrote:
> > 
> > - This also showed up a number of buggy prepare_write / commit_write
> >   implementations that were setting the page uptodate in the prepare_write
> >   side: bad! this allows uninitialised data to be read. Fix these.
> 
> Well.  It's non-buggy under the current protocol because the page remains
> locked throughout.  This patch would make these ->prepare_write()
> implementations buggy.

But if it becomes uptodate, then do_generic_mapping_read can read it
without locking it (and so can filemap_nopage at present, although it
looks like that's going to take the page lock soon).

> > +#ifdef CONFIG_DEBUG_VM
> > +			fault_in_pages_readable(buf, bytes);
> > +#endif
> 
> I'll need to remember to take that out later on.  Or reorder the patches, I
> guess.
> 
> >  int simple_commit_write(struct file *file, struct page *page,
> > -			unsigned offset, unsigned to)
> > +			unsigned from, unsigned to)
> >  {
> > -	struct inode *inode = page->mapping->host;
> > -	loff_t pos = ((loff_t)page->index << PAGE_CACHE_SHIFT) + to;
> > -
> > -	/*
> > -	 * No need to use i_size_read() here, the i_size
> > -	 * cannot change under us because we hold the i_mutex.
> > -	 */
> > -	if (pos > inode->i_size)
> > -		i_size_write(inode, pos);
> > -	set_page_dirty(page);
> > +	if (to > from) {
> > +		struct inode *inode = page->mapping->host;
> > +		loff_t pos = ((loff_t)page->index << PAGE_CACHE_SHIFT) + to;
> > +
> > +		if (to - from == PAGE_CACHE_SIZE)
> > +			SetPageUptodate(page);
> 
> This SetPageUptodate() can go away?

It is needed because the prepare_write does not try to bring the page
uptodate if it is a full page write. (I was considering another patch
to just remove that completely, as it might be overkill for something
like sysfs, but it demonstrates the principle quite nicely).

> 
> > @@ -2317,17 +2320,6 @@ int nobh_prepare_write(struct page *page
> >  
> >  	if (is_mapped_to_disk)
> >  		SetPageMappedToDisk(page);
> > -	SetPageUptodate(page);
> > -
> > -	/*
> > -	 * Setting the page dirty here isn't necessary for the prepare_write
> > -	 * function - commit_write will do that.  But if/when this function is
> > -	 * used within the pagefault handler to ensure that all mmapped pages
> > -	 * have backing space in the filesystem, we will need to dirty the page
> > -	 * if its contents were altered.
> > -	 */
> > -	if (dirtied_it)
> > -		set_page_dirty(page);
> >  
> >  	return 0;
> 
> Local variable `dirtied_it' can go away now.
> 
> Or can it?  We've modified the page's contents.  If the copy_from_user gets
> a fault and we do a zero-length ->commit_write(), nobody ends up dirtying
> the page.

But only if the page is not uptodate. Otherwise we won't modify its contents
(no need to).

> > @@ -2450,6 +2436,7 @@ int nobh_truncate_page(struct address_sp
> >  		memset(kaddr + offset, 0, PAGE_CACHE_SIZE - offset);
> >  		flush_dcache_page(page);
> >  		kunmap_atomic(kaddr, KM_USER0);
> > +		SetPageUptodate(page);
> >  		set_page_dirty(page);
> >  	}
> >  	unlock_page(page);
> 
> I've already forgotten why this was added.  Comment, please ;)

Well, nobh_prepare_write no longer sets it uptodate, so we need to if
we're going to set_page_dirty. OTOH, why does truncate_page need to
zero the pagecache anyway? I wonder if we couldn't delete this whole
function? (not in this patchset!)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-10-14  4:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 16:43 [rfc] buffered write deadlock fix Nick Piggin
2006-10-13 16:44 ` [patch 1/6] mm: revert "generic_file_buffered_write(): handle zero length iovec segments" Nick Piggin, Andrew Morton
2006-10-13 16:44 ` [patch 2/6] mm: revert "generic_file_buffered_write(): deadlock on vectored write" Nick Piggin, Andrew Morton
2006-10-13 16:44 ` [patch 3/6] mm: generic_file_buffered_write cleanup Nick Piggin, Andrew Morton
2006-10-13 16:44 ` [patch 4/6] mm: comment mmap_sem / lock_page lockorder Nick Piggin
2006-10-13 16:44 ` [patch 5/6] mm: debug write deadlocks Nick Piggin
2006-10-13 16:44 ` [patch 6/6] mm: fix pagecache " Nick Piggin, Andrew Morton
2006-10-13 22:14   ` Andrew Morton
2006-10-14  4:19     ` Nick Piggin [this message]
2006-10-14  4:30       ` Nick Piggin
2006-10-15 11:35       ` Peter Zijlstra
2006-10-14  5:04   ` Nick Piggin
2006-10-15 11:37   ` Peter Zijlstra
2006-10-15 11:56     ` Nick Piggin
2006-10-15 13:51       ` Peter Zijlstra
2006-10-15 14:19         ` SPAM: " Nick Piggin
2006-10-15 15:47           ` Peter Zijlstra
2006-10-15 15:57             ` RRe: " Nick Piggin
2006-10-15 16:13               ` Peter Zijlstra
2006-10-16 15:24                 ` pagefault_disable (was Re: [patch 6/6] mm: fix pagecache write deadlocks) Nick Piggin
2006-10-16 16:05                   ` Peter Zijlstra
2006-10-16 16:12                     ` Nick Piggin
2006-10-18 14:25   ` [patch 6/6] mm: fix pagecache write deadlocks Chris Mason

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=20061014041927.GA14467@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=aia21@cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=neilb@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox