From: Shaohua Li <shaohua.li@intel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>
Subject: Re: [BUG] infinite loop in find_get_pages()
Date: Wed, 14 Sep 2011 16:55:19 +0800 [thread overview]
Message-ID: <1315990519.29510.119.camel@sli10-conroe> (raw)
In-Reply-To: <1315989783.2361.7.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
On Wed, 2011-09-14 at 16:43 +0800, Eric Dumazet wrote:
> Le mercredi 14 septembre 2011 à 16:20 +0800, Shaohua Li a écrit :
> > 2011/9/14 Shaohua Li <shli@kernel.org>:
> > > it appears we didn't account skipped swap entry in find_get_pages().
> > > does the attached patch help?
> > I can easily reproduce the issue. Just cp files in tmpfs, trigger swap and
> > drop caches. The debug patch fixes it at my side.
> > Eric, please try it.
> >
>
> Hello Shaohua
>
> I tried it with added traces :
>
>
> [ 277.077855] mv used greatest stack depth: 3336 bytes left
> [ 310.558012] nr_found=2 nr_skip=2
> [ 310.558139] nr_found=14 nr_skip=14
> [ 332.195162] nr_found=2 nr_skip=2
> [ 332.195274] nr_found=14 nr_skip=14
> [ 352.315273] nr_found=14 nr_skip=14
> [ 372.673575] nr_found=14 nr_skip=14
> [ 397.115463] nr_found=14 nr_skip=14
> [ 403.391694] cc1 used greatest stack depth: 3184 bytes left
> [ 404.761194] cc1 used greatest stack depth: 2640 bytes left
> [ 417.306510] nr_found=14 nr_skip=14
> [ 440.198051] nr_found=14 nr_skip=14
>
> I also used :
>
> - if (unlikely(!ret && nr_found))
> + if (unlikely(!ret && nr_found > nr_skip))
> goto restart;
nr_found > nr_skip is better
> It seems to fix the bug. I suspect it also aborts
> invalidate_mapping_pages() if we skip 14 pages, but existing comment
> states its OK :
>
> /*
> * Note: this function may get called on a shmem/tmpfs mapping:
> * pagevec_lookup() might then return 0 prematurely (because it
> * got a gangful of swap entries); but it's hardly worth worrying
> * about - it can rarely have anything to free from such a mapping
> * (most pages are dirty), and already skips over any difficulties.
> */
that might be a problem, let Hugh answer if it is.
Thanks,
Shaohua
next prev parent reply other threads:[~2011-09-14 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 19:23 Eric Dumazet
2011-09-13 23:53 ` Andrew Morton
2011-09-14 0:21 ` Eric Dumazet
2011-09-14 0:34 ` Lin Ming
2011-09-15 10:47 ` Pawel Sikora
2011-09-15 11:11 ` Justin Piszcz
2011-09-15 12:04 ` Eric Dumazet
2011-09-15 15:00 ` Paweł Sikora
2011-09-15 15:15 ` Eric Dumazet
[not found] ` <CA+55aFyG3-3_gqGjqUmsTAHWfmNLMdQVf4XqUZrDAGMBxgur=Q@mail.gmail.com>
2011-09-14 6:48 ` Linus Torvalds
2011-09-14 6:53 ` Eric Dumazet
2011-09-14 7:32 ` Shaohua Li
2011-09-14 8:20 ` Shaohua Li
2011-09-14 8:43 ` Eric Dumazet
2011-09-14 8:55 ` Shaohua Li [this message]
2011-09-14 20:38 ` Hugh Dickins
2011-09-14 20:55 ` Eric Dumazet
2011-09-14 21:53 ` Hugh Dickins
2011-09-14 22:08 ` Eric Dumazet
2011-09-14 22:37 ` Linus Torvalds
2011-09-15 0:45 ` Shaohua Li
2011-09-15 2:00 ` Hugh Dickins
2011-09-15 4:02 ` Eric Dumazet
[not found] ` <CA+55aFx41_Z4TjjJwPuE21Q8oD3aGWtQwh45DUiCjPVD-wCJXw@mail.gmail.com>
2011-09-14 6:48 ` Linus Torvalds
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=1315990519.29510.119.camel@sli10-conroe \
--to=shaohua.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®