mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Pankaj Suryawanshi <pankaj.suryawanshi@einfochips.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"minchan@kernel.org" <minchan@kernel.org>
Subject: Re: vmscan: Reclaim unevictable pages
Date: Thu, 14 Mar 2019 09:41:20 +0100	[thread overview]
Message-ID: <20190314084120.GF7473@dhcp22.suse.cz> (raw)
In-Reply-To: <SG2PR02MB3098B751EC6B8E32806A42FBE84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>

On Thu 14-03-19 08:23:10, Pankaj Suryawanshi wrote:
> 
> Below is the Error Msg :
> 
> [   24.718792] page dumped because: VM_BUG_ON_PAGE(PageLRU(page) || PageUnevictable(page))
> [   24.726949] page->mem_cgroup:bd008c00
> [   24.730693] ------------[ cut here ]------------
> [   24.735304] kernel BUG at mm/vmscan.c:1350!
> [   24.739478] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM

Just curious. Which kernel version is that? Are there any addional
patches applied on top of vanilla?
 
> Solved the issue by below patch.
> 
> 
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index be56e2e..2e51edc 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -990,15 +990,17 @@ static unsigned long shrink_page_list(struct list_head *page_list,
>                 page = lru_to_page(page_list);
>                 list_del(&page->lru);
> 
>                if (!trylock_page(page)) {
>                         goto keep;
>                }
> 
>                 VM_BUG_ON_PAGE(PageActive(page), page);
> 
>                 sc->nr_scanned++;
> 
>                 if (unlikely(!page_evictable(page)))
> -                       goto activate_locked;
> +                      goto cull_mlocked;
> 
>                 if (!sc->may_unmap && page_mapped(page))
>                         goto keep_locked;
> @@ -1331,6 +1333,12 @@ static unsigned long shrink_page_list(struct list_head *page_list,
>                 } else
>                         list_add(&page->lru, &free_pages);
>                 continue;
> +cull_mlocked:
> +                if (PageSwapCache(page))
> +                        try_to_free_swap(page);
> +                unlock_page(page);
> +                list_add(&page->lru, &ret_pages);
> +                continue;
> 
>  activate_locked:
>                 /* Not a candidate for swapping, so reclaim swap space. */
> 
> 
> 
> 
> From: Pankaj Suryawanshi
> Sent: 14 March 2019 13:23:53
> To: linux-kernel@vger.kernel.org
> Cc: minchan@kernel.org
> Subject: vmscan: Reclaim unevictable pages
> 
> 
> 
> Hello ,
> 
> shrink_page_list() returns , number of pages reclaimed, when pages is unevictable it returns VM_BUG_ON_PAGE(PageLRU(page) || PageUnevicatble(page),page);
> 
> We can add the unevictable pages in reclaim list in shrink_page_list(), return total number of reclaim pages including unevictable pages, let the caller handle unevictable pages.
> 
> Regards,
> Pankaj
> 
> ************************************************************************************************************************************************************* eInfochips Business Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated. Company has taken enough precautions to prevent the spread of viruses. However the company 
 accepts no liability for any damage caused by any virus transmitted by this email. *************************************************************************************************************************************************************

-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2019-03-14  8:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SG2PR02MB3098A05E09B0D3F3CB1C3B9BE84B0@SG2PR02MB3098.apcprd02.prod.outlook.com>
2019-03-14  7:53 ` Pankaj Suryawanshi
2019-03-14  8:23   ` Pankaj Suryawanshi
2019-03-14  8:41     ` Michal Hocko [this message]
2019-03-14  8:52       ` [External] " Pankaj Suryawanshi
2019-03-14  9:25         ` Kirill Tkhai
2019-03-14 11:09           ` Pankaj Suryawanshi
2019-03-14 13:44             ` Pankaj Suryawanshi
2019-03-15  6:05               ` Pankaj Suryawanshi
2019-03-15 10:11                 ` Pankaj Suryawanshi
2019-03-18  7:45                   ` Pankaj Suryawanshi
2019-03-18  8:56                     ` Pankaj Suryawanshi
2019-03-18  8:42                   ` [External] " Vlastimil Babka
2019-03-18  9:09                     ` Pankaj Suryawanshi
2019-03-18  9:33                       ` Kirill Tkhai
2019-03-18  9:43                         ` Pankaj Suryawanshi
2019-03-18  9:47                           ` Kirill Tkhai
2019-03-18  9:59                             ` Pankaj Suryawanshi
2019-03-18 10:38                               ` Kirill Tkhai
2019-03-20  6:48                                 ` Pankaj Suryawanshi
2019-03-26  7:53                                   ` Pankaj Suryawanshi
2019-03-26  9:01                                     ` Michal Hocko
2019-03-26  9:12                                       ` Pankaj Suryawanshi
2019-03-26  9:16                                       ` Pankaj Suryawanshi
2019-03-26  9:36                                         ` Michal Hocko
2019-03-29  5:29                                           ` Pankaj Suryawanshi

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=20190314084120.GF7473@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=pankaj.suryawanshi@einfochips.com \
    /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®