linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yuri Norov <ynorov@marvell.com>
To: Qian Cai <cai@lca.pw>, Dexuan-Linux Cui <dexuan.linux@gmail.com>,
	"Mike Kravetz" <mike.kravetz@oracle.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	Andrea Parri <andrea.parri@amarulasolutions.com>,
	"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
	Michal Hocko <mhocko@suse.com>, Minchan Kim <minchan@kernel.org>,
	Hugh Dickins <hughd@google.com>, Dexuan Cui <decui@microsoft.com>,
	"v-lide@microsoft.com" <v-lide@microsoft.com>,
	"Yury Norov" <yury.norov@gmail.com>
Subject: Re: [EXT] Re: [PATCH -mm] mm, swap: Fix bad swap file entry warning
Date: Fri, 31 May 2019 22:36:03 +0000	[thread overview]
Message-ID: <BN6PR1801MB2065F9E5FF6F9E8928879290CB190@BN6PR1801MB2065.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1559330205.6132.40.camel@lca.pw>

[-- Attachment #1: Type: text/plain, Size: 2435 bytes --]




________________________________
From: Qian Cai <cai@lca.pw>
Sent: Friday, May 31, 2019 11:16 PM
To: Dexuan-Linux Cui; Mike Kravetz
Cc: Huang, Ying; Andrew Morton; linux-mm@kvack.org; Linux Kernel Mailing List; Andrea Parri; Paul E . McKenney; Michal Hocko; Minchan Kim; Hugh Dickins; Dexuan Cui; v-lide@microsoft.com; Yuri Norov
Subject: [EXT] Re: [PATCH -mm] mm, swap: Fix bad swap file entry warning
----------------------------------------------------------------------
> On Fri, 2019-05-31 at 11:27 -0700, Dexuan-Linux Cui wrote:
> > Hi,
> > Did you know about the panic reported here:
> > https://marc.info/?t=155930773000003&r=1&w=2
> >
> > "Kernel panic - not syncing: stack-protector: Kernel stack is
> > corrupted in: write_irq_affinity.isra> "
> >
> > This panic is reported on PowerPC and x86.
> >
> > In the case of x86, we see a lot of "get_swap_device: Bad swap file entry"
> > errors before the panic:
> >
> > ...
> > [   24.404693] get_swap_device: Bad swap file entry 5800000000000001
> > [   24.408702] get_swap_device: Bad swap file entry 5c00000000000001
> > [   24.412510] get_swap_device: Bad swap file entry 6000000000000001
> > [   24.416519] get_swap_device: Bad swap file entry 6400000000000001
> > [   24.420217] get_swap_device: Bad swap file entry 6800000000000001
> > [   24.423921] get_swap_device: Bad swap file entry 6c00000000000001

[..]

I don't have a panic, but I observe many lines like this.

> Looks familiar,
>
> https://lore.kernel.org/lkml/1559242868.6132.35.camel@lca.pw/<https://lore.kernel.org/lkml/1559242868.6132.35.camel@lca.pw/>
>
> I suppose Andrew might be better of reverting the whole series first before Yury
> came up with a right fix, so that other people who is testing linux-next don't
> need to waste time for the same problem.

I didn't observe any problems with this series on top of 5.1, and there's a fix for swap that eliminates
the problem on top of current next for me:
https://lkml.org/lkml/2019/5/30/1630


<https://lkml.org/lkml/2019/5/30/1630>
LKML: "Huang, Ying": [PATCH -mm] mm, swap: Fix bad swap file entry warning<https://lkml.org/lkml/2019/5/30/1630>
lkml.org
From: Huang Ying <ying.huang@intel.com> Mike reported the following warning messages get_swap_device: Bad swap file entry 1400000000000001 This is produced by
Could you please test your series with the patch of Huang Ying?

Thanks,
Yury

[-- Attachment #2: Type: text/html, Size: 6732 bytes --]

      reply	other threads:[~2019-05-31 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31  2:41 Huang, Ying
2019-05-31  6:10 ` Michal Hocko
2019-06-01  0:14   ` Huang, Ying
2019-05-31 16:59 ` Mike Kravetz
2019-05-31 18:27   ` Dexuan-Linux Cui
2019-05-31 19:16     ` Qian Cai
2019-05-31 22:36       ` Yuri Norov [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=BN6PR1801MB2065F9E5FF6F9E8928879290CB190@BN6PR1801MB2065.namprd18.prod.outlook.com \
    --to=ynorov@marvell.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=cai@lca.pw \
    --cc=decui@microsoft.com \
    --cc=dexuan.linux@gmail.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=minchan@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=v-lide@microsoft.com \
    --cc=ying.huang@intel.com \
    --cc=yury.norov@gmail.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