From: "Huang\, Ying" <ying.huang@intel.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: <akpm@linux-foundation.org>, <broonie@kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-next@vger.kernel.org>,
<mhocko@suse.cz>, <mm-commits@vger.kernel.org>,
<sfr@canb.auug.org.au>
Subject: Re: mmotm 2019-05-29-20-52 uploaded
Date: Fri, 31 May 2019 10:42:35 +0800 [thread overview]
Message-ID: <87h89b5opw.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <87lfyn5rgu.fsf@yhuang-dev.intel.com> (Ying Huang's message of "Fri, 31 May 2019 09:43:13 +0800")
"Huang, Ying" <ying.huang@intel.com> writes:
> Hi, Mike,
>
> Mike Kravetz <mike.kravetz@oracle.com> writes:
>
>> On 5/29/19 8:53 PM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2019-05-29-20-52 has been uploaded to
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>
>> With this kernel, I seem to get many messages such as:
>>
>> get_swap_device: Bad swap file entry 1400000000000001
>>
>> It would seem to be related to commit 3e2c19f9bef7e
>>> * mm-swap-fix-race-between-swapoff-and-some-swap-operations.patch
>
> Hi, Mike,
>
> Thanks for reporting! I find an issue in my patch and I can reproduce
> your problem now. The reason is total_swapcache_pages() will call
> get_swap_device() for invalid swap device. So we need to find a way to
> silence the warning. I will post a fix ASAP.
I have sent out a fix patch in another thread with title
"[PATCH -mm] mm, swap: Fix bad swap file entry warning"
Can you try it?
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2019-05-31 2:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 3:53 mmotm 2019-05-29-20-52 uploaded akpm
2019-05-30 4:43 ` Luigi Semenzato
2019-05-31 3:50 ` Stephen Rothwell
2019-05-30 20:54 ` Mike Kravetz
2019-05-31 1:43 ` Huang, Ying
2019-05-31 2:42 ` Huang, Ying [this message]
2019-05-30 22:28 ` mmotm 2019-05-29-20-52 uploaded (mpls) Randy Dunlap
2019-06-04 22:28 ` mmotm 2019-05-29-20-52 uploaded (mpls) +linux-next Randy Dunlap
2019-06-07 0:24 ` Matteo Croce
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=87h89b5opw.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mike.kravetz@oracle.com \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).