Re: Does swap_set_page_dirty() calling ->set_page_dirty() make sense?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 17, 2012 at 12:15:46PM -0700, Hugh Dickins wrote:
> On Mon, 17 Sep 2012, Jan Kara wrote:
> > 
> >   I tripped over a crash in reiserfs which happened due to PageSwapCache
> > page being passed to reiserfs_set_page_dirty(). Now it's not that hard to
> > make reiserfs_set_page_dirty() check that case but I really wonder: Does it
> > make sense to call mapping->a_ops->set_page_dirty() for a PageSwapCache
> > page? The page is going to be written via direct IO so from the POV of the
> > filesystem there's no need for any dirtiness tracking. Also there are
> > several ->set_page_dirty() implementations which will spectacularly crash
> > because they do things like page->mapping->host, or call
> > __set_page_dirty_buffers() which expects buffer heads in page->private.
> > Or what is the reason for calling filesystem's set_page_dirty() function?
> 
> This is a question for Mel, really: it used not to call the filesystem.
> 

And now it should only be called if SWP_FILE is set to perform read/write
of pages through the filesystem. In practice I only expect this to happen
when a swapfile is activated on NFS.

> But my reading of the 3.6 code says that it still will not call the
> filesystem, unless the filesystem (only nfs) provides a swap_activate
> method, which should be the only case in which SWP_FILE gets set.
> And I rather think Mel does want to use the filesystem set_page_dirty
> in that case.  Am I misreading?
> 

That was the intention at least.

> Did you see this on a vanilla kernel?  Or is it possible that you have
> a private patch merged in, with something else sharing the SWP_FILE bit
> (defined in include/linux/swap.h) by mistake?
> 

I see that Jan followed up that this was observed on SLES. The
implementaiton there is based on a much earlier revision of
swap-over-NFS than what was finally merged to mainline. I'll check it
out.

Thanks.

-- 
Mel Gorman
SUSE Labs

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


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]