All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Hugh Dickins <hughd@google.com>
Cc: Jan Kara <jack@suse.cz>, linux-mm@kvack.org
Subject: Re: Does swap_set_page_dirty() calling ->set_page_dirty() make sense?
Date: Tue, 18 Sep 2012 10:58:08 +0100	[thread overview]
Message-ID: <20120918095808.GJ11266@suse.de> (raw)
In-Reply-To: <alpine.LSU.2.00.1209171204100.6720@eggly.anvils>

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@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>

      parent reply	other threads:[~2012-09-18  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 16:35 Does swap_set_page_dirty() calling ->set_page_dirty() make sense? Jan Kara
2012-09-17 19:15 ` Hugh Dickins
2012-09-18  2:16   ` Jan Kara
2012-09-18  8:51     ` Petr Tesarik
2012-09-18 10:02       ` Mel Gorman
2012-09-18  9:58   ` Mel Gorman [this message]

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=20120918095808.GJ11266@suse.de \
    --to=mgorman@suse.de \
    --cc=hughd@google.com \
    --cc=jack@suse.cz \
    --cc=linux-mm@kvack.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.