From: "Huang\, Ying" <ying.huang@intel.com>
To: Minchan Kim <minchan@kernel.org>
Cc: "Huang, Ying" <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Tim Chen <tim.c.chen@linux.intel.com>,
Michal Hocko <mhocko@suse.com>,
stable@vger.kernel.org, Christian Kujau <lists@nerdbynature.de>
Subject: Re: [PATCH -mm] mm, swap: Fix false error message in __swp_swapcount()
Date: Wed, 25 Oct 2017 10:32:52 +0800 [thread overview]
Message-ID: <8737686jor.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20171024201708.GA25022@bgram> (Minchan Kim's message of "Wed, 25 Oct 2017 05:17:08 +0900")
Minchan Kim <minchan@kernel.org> writes:
> On Tue, Oct 24, 2017 at 10:47:00AM +0800, Huang, Ying wrote:
>> From: Ying Huang <ying.huang@intel.com>
>>
>> __swp_swapcount() is used in __read_swap_cache_async(). Where the
>> invalid swap entry (offset > max) may be supplied during swap
>> readahead. But __swp_swapcount() will print error message for these
>> expected invalid swap entry as below, which will make the users
>> confusing.
>>
>> swap_info_get: Bad swap offset entry 0200f8a7
>>
>> So the swap entry checking code in __swp_swapcount() is changed to
>> avoid printing error message for it. To avoid to duplicate code with
>> __swap_duplicate(), a new helper function named
>> __swap_info_get_silence() is added and invoked in both places.
>
> It's the problem caused by readahead, not __swap_info_get which is low-end
> primitive function. Instead, please fix high-end swapin_readahead to limit
> to last valid block as handling to avoid swap header which is special case,
> too.
Yes. You are right, will send the new version.
Best Regards,
Huang, Ying
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Minchan Kim <minchan@kernel.org>
Cc: "Huang\, Ying" <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
"Michal Hocko" <mhocko@suse.com>, <stable@vger.kernel.org>,
Christian Kujau <lists@nerdbynature.de>
Subject: Re: [PATCH -mm] mm, swap: Fix false error message in __swp_swapcount()
Date: Wed, 25 Oct 2017 10:32:52 +0800 [thread overview]
Message-ID: <8737686jor.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20171024201708.GA25022@bgram> (Minchan Kim's message of "Wed, 25 Oct 2017 05:17:08 +0900")
Minchan Kim <minchan@kernel.org> writes:
> On Tue, Oct 24, 2017 at 10:47:00AM +0800, Huang, Ying wrote:
>> From: Ying Huang <ying.huang@intel.com>
>>
>> __swp_swapcount() is used in __read_swap_cache_async(). Where the
>> invalid swap entry (offset > max) may be supplied during swap
>> readahead. But __swp_swapcount() will print error message for these
>> expected invalid swap entry as below, which will make the users
>> confusing.
>>
>> swap_info_get: Bad swap offset entry 0200f8a7
>>
>> So the swap entry checking code in __swp_swapcount() is changed to
>> avoid printing error message for it. To avoid to duplicate code with
>> __swap_duplicate(), a new helper function named
>> __swap_info_get_silence() is added and invoked in both places.
>
> It's the problem caused by readahead, not __swap_info_get which is low-end
> primitive function. Instead, please fix high-end swapin_readahead to limit
> to last valid block as handling to avoid swap header which is special case,
> too.
Yes. You are right, will send the new version.
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Minchan Kim <minchan@kernel.org>
Cc: "Huang\, Ying" <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
"Michal Hocko" <mhocko@suse.com>, <stable@vger.kernel.org>,
Christian Kujau <lists@nerdbynature.de>
Subject: Re: [PATCH -mm] mm, swap: Fix false error message in __swp_swapcount()
Date: Wed, 25 Oct 2017 10:32:52 +0800 [thread overview]
Message-ID: <8737686jor.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20171024201708.GA25022@bgram> (Minchan Kim's message of "Wed, 25 Oct 2017 05:17:08 +0900")
Minchan Kim <minchan@kernel.org> writes:
> On Tue, Oct 24, 2017 at 10:47:00AM +0800, Huang, Ying wrote:
>> From: Ying Huang <ying.huang@intel.com>
>>
>> __swp_swapcount() is used in __read_swap_cache_async(). Where the
>> invalid swap entry (offset > max) may be supplied during swap
>> readahead. But __swp_swapcount() will print error message for these
>> expected invalid swap entry as below, which will make the users
>> confusing.
>>
>> swap_info_get: Bad swap offset entry 0200f8a7
>>
>> So the swap entry checking code in __swp_swapcount() is changed to
>> avoid printing error message for it. To avoid to duplicate code with
>> __swap_duplicate(), a new helper function named
>> __swap_info_get_silence() is added and invoked in both places.
>
> It's the problem caused by readahead, not __swap_info_get which is low-end
> primitive function. Instead, please fix high-end swapin_readahead to limit
> to last valid block as handling to avoid swap header which is special case,
> too.
Yes. You are right, will send the new version.
Best Regards,
Huang, Ying
--
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>
next prev parent reply other threads:[~2017-10-25 2:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 2:47 [PATCH -mm] mm, swap: Fix false error message in __swp_swapcount() Huang, Ying
2017-10-24 2:47 ` Huang, Ying
2017-10-24 8:38 ` Michal Hocko
2017-10-24 8:38 ` Michal Hocko
2017-10-24 15:15 ` Huang, Ying
2017-10-24 15:15 ` Huang, Ying
2017-10-24 15:15 ` Huang, Ying
2017-10-24 15:30 ` Michal Hocko
2017-10-24 15:30 ` Michal Hocko
2017-10-24 15:34 ` Huang, Ying
2017-10-24 15:34 ` Huang, Ying
2017-10-24 15:34 ` Huang, Ying
2017-10-24 20:17 ` Minchan Kim
2017-10-24 20:17 ` Minchan Kim
2017-10-25 2:32 ` Huang, Ying [this message]
2017-10-25 2:32 ` Huang, Ying
2017-10-25 2:32 ` Huang, Ying
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=8737686jor.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lists@nerdbynature.de \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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 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.