From: Yang Shi <yang.shi@linux.alibaba.com>
To: Tim Chen <tim.c.chen@linux.intel.com>,
ying.huang@intel.com, tim.c.chen@intel.com, minchan@kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] mm: swap: check if swap backing device is congested or not
Date: Wed, 19 Dec 2018 15:48:53 -0800 [thread overview]
Message-ID: <385ffd4f-d903-6e2f-e80e-7d3797885c54@linux.alibaba.com> (raw)
In-Reply-To: <50e14a30-97bb-06c6-ae6a-74e6dc827713@linux.intel.com>
On 12/19/18 11:00 AM, Tim Chen wrote:
> On 12/19/18 10:40 AM, Yang Shi wrote:
>>
>>>>> I don't think your dereference inode = si->swap_file->f_mapping->host
>>>>> is always safe. You should do it only when (si->flags & SWP_FS) is true.
>>>> Do you mean it is not safe for swap partition?
>>> The f_mapping may not be instantiated. It is only done for SWP_FS.
>> Really? I saw the below calls in swapon:
>>
>> swap_file = file_open_name(name, O_RDWR|O_LARGEFILE, 0);
>> ...
>> p->swap_file = swap_file;
>> mapping = swap_file->f_mapping;
>> inode = mapping->host;
>> ...
>>
>> Then the below code manipulates the inode.
>>
>> And, trace shows file_open_name() does call blkdev_open if it is turning block device swap on. And, blkdev_open() would return instantiated address_space and inode.
>>
>> Am I missing something?
>>
> I was trying to limit the congestion logic for block devices backed swap.
> So the check I had in mind should really be "si->flags & SWP_BLKDEV"
> instead of si->flags & SWP_FS. I was concerned that there could
> be other use cases where the inode dereference is invalid.
>
> Looking at the code a bit more, looks like swap_cluster_readahead is not
> used for other special case swap usage (like page migration). So
> you would a proper swapfile and inode here. But I think it is still
Yes, just swap page fault and shmem calls this function. Actually, your
above concern is valid if the inode were added into swap_address_space
(address_space->host). I did this in my first attempt, and found out it
may break some assumption in clear_page_dirty_for_io() and migration.
So, I made the patch as it is.
> a good idea to have a check for SWP_BLKDEV in si->flags.
I don't get your point why it should be block dev swap only. IMHO, block
dev swap should be less likely fragmented and congested than swap file,
right? Block dev swap could be a dedicated physical device, but swap
file has to be with filesystem.
It sounds reasonable to me to have this check for swap file only.
However, to be honest, it sounds not hurt to have both.
Thanks,
Yang
>
> Thanks.
>
> Tim
>
>
next prev parent reply other threads:[~2018-12-19 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 6:52 Yang Shi
2018-12-18 6:52 ` [RFC PATCH 2/2] mm: swap: add comment for swap_vma_readahead Yang Shi
2018-12-18 19:29 ` [RFC PATCH 1/2] mm: swap: check if swap backing device is congested or not Tim Chen
2018-12-18 23:43 ` Yang Shi
2018-12-19 0:16 ` Tim Chen
2018-12-19 5:56 ` Yang Shi
2018-12-19 17:28 ` Tim Chen
2018-12-19 18:40 ` Yang Shi
2018-12-19 19:00 ` Tim Chen
2018-12-19 23:48 ` Yang Shi [this message]
2018-12-20 1:05 ` Tim Chen
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=385ffd4f-d903-6e2f-e80e-7d3797885c54@linux.alibaba.com \
--to=yang.shi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=tim.c.chen@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox