kernel/linux.git, branch v2.6.17-rc1

Linux v2.6.17-rc1

2006-04-03T03:22:10+00:00

Close of the merge window..

Update dummy snd_power_wait() function for new calling convention

2006-04-02T21:37:36+00:00

Apparently nobody had tried to compile the ALSA CVS tree without power management enabled. Signed-off-by: Linus Torvalds

Merge branch 'splice' of git://brick.kernel.dk/data/git/linux-2.6-block

2006-04-02T21:22:06+00:00

* 'splice' of git://brick.kernel.dk/data/git/linux-2.6-block: [PATCH] splice: fix page stealing LRU handling. [PATCH] splice: page stealing needs to wait_on_page_writeback() [PATCH] splice: export generic_splice_sendpage [PATCH] splice: add a SPLICE_F_MORE flag [PATCH] splice: add comments documenting more of the code [PATCH] splice: improve writeback and clean up page stealing [PATCH] splice: fix shadow[] filling logic

[PATCH] splice: fix page stealing LRU handling.

2006-04-02T21:11:04+00:00

Originally from Nick Piggin, just adapted to the newer branch. You can't check PageLRU without holding zone->lru_lock. The page release code can get away with it only because the page refcount is 0 at that point. Also, you can't reliably remove pages from the LRU unless the refcount is 0. Ever. Signed-off-by: Nick Piggin Signed-off-by: Jens Axboe

[PATCH] splice: page stealing needs to wait_on_page_writeback()

2006-04-02T21:10:32+00:00

Thanks to Andrew for the good explanation of why this is so. akpm writes: If a page is under writeback and we remove it from pagecache, it's still going to get written to disk. But the VFS no longer knows about that page, nor that this page is about to modify disk blocks. So there might be scenarios in which those blocks-which-are-about-to-be-written-to get reused for something else. When writeback completes, it'll scribble on those blocks. This won't happen in ext2/ext3-style filesystems in normal mode because the page has buffers and try_to_release_page() will fail. But ext2 in nobh mode doesn't attach buffers at all - it just sticks the page in a BIO, finds some new blocks, points the BIO at those blocks and lets it rip. While that write IO's in flight, someone could truncate the file. Truncate won't block on the writeout because the page isn't in pagecache any more. So truncate will the free the blocks from the file under the page's feet. Then something else can reallocate those blocks. Then write data to them. Now, the original write completes, corrupting the filesystem. Signed-off-by: Jens Axboe

[PATCH] splice: export generic_splice_sendpage

2006-04-02T21:06:05+00:00

Forgot that one, thanks Jeff. Also move the other EXPORT_SYMBOL to right below the functions. Signed-off-by: Jens Axboe

[PATCH] splice: add a SPLICE_F_MORE flag

2006-04-02T21:05:41+00:00

This lets userspace indicate whether more data will be coming in a subsequent splice call. Signed-off-by: Jens Axboe

[PATCH] splice: add comments documenting more of the code

2006-04-02T21:05:09+00:00

Hopefully this will make Andrew a little more happy. Signed-off-by: Jens Axboe

[PATCH] splice: improve writeback and clean up page stealing

2006-04-02T21:04:46+00:00

By cleaning up the writeback logic (killing write_one_page() and the manual set_page_dirty()), we can get rid of ->stolen inside the pipe_buffer and just keep it local in pipe_to_file(). This also adds dirty page balancing logic and O_SYNC handling. Signed-off-by: Jens Axboe

[PATCH] splice: fix shadow[] filling logic

2006-04-02T21:04:21+00:00

Clear the entire range, and don't increment pidx or we keep filling the same position again and again. Thanks to KAMEZAWA Hiroyuki. Signed-off-by: Jens Axboe