linux-kernel - Re: [RFC PATCH 1/2] mm: swap: check if swap backing device is congested or not

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c0290c77-87ba-32bf-8ed0-d42a322d3d06@linux.intel.com>
Date:   Tue, 18 Dec 2018 16:16:06 -0800
From:   Tim Chen <tim.c.chen@...ux.intel.com>
To:     Yang Shi <yang.shi@...ux.alibaba.com>, ying.huang@...el.com,
        tim.c.chen@...el.com, minchan@...nel.org,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/2] mm: swap: check if swap backing device is
 congested or not

On 12/18/18 3:43 PM, Yang Shi wrote:
> 
> 
> On 12/18/18 11:29 AM, Tim Chen wrote:
>> On 12/17/18 10:52 PM, Yang Shi wrote:
>>
>>> diff --git a/mm/swap_state.c b/mm/swap_state.c
>>> index fd2f21e..7cc3c29 100644
>>> --- a/mm/swap_state.c
>>> +++ b/mm/swap_state.c
>>> @@ -538,11 +538,15 @@ struct page *swap_cluster_readahead(swp_entry_t entry, gfp_t gfp_mask,
>>>       bool do_poll = true, page_allocated;
>>>       struct vm_area_struct *vma = vmf->vma;
>>>       unsigned long addr = vmf->address;
>>> +    struct inode *inode = si->swap_file->f_mapping->host;
>>>         mask = swapin_nr_pages(offset) - 1;
>>>       if (!mask)
>>>           goto skip;
>>>   
>> Shmem will also be using this function and I don't think the inode_read_congested
>> logic is relevant for that case.
> 
> IMHO, shmem is also relevant. As long as it is trying to readahead from swap, it should check if the underlying device is busy or not regardless of shmem or anon page.
> 

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.

Tim