linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linux.alibaba.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linmiaohe@huawei.com, akpm@linux-foundation.org,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Hugh Dickins <hughd@google.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [REF PATCH] mm/swap: fix swapon failure
Date: Mon, 9 Nov 2020 20:36:08 +0800	[thread overview]
Message-ID: <46e34498-01aa-3442-eee3-d3b84a00e1a8@linux.alibaba.com> (raw)
In-Reply-To: <88fb2ed0-cb0c-2b4b-a73e-3a64fdc0a2cd@linux.alibaba.com>



在 2020/11/9 下午8:17, Alex Shi 写道:
> 
> 
> 在 2020/11/9 下午8:07, Matthew Wilcox 写道:
>> On Mon, Nov 09, 2020 at 07:47:16PM +0800, Alex Shi wrote:
>>> Go through the context I found the exit_swap_address_space(p->type)
>>> shouldn't be used in good result path. So just move it to error path.
>>
>> But ... it's not used in the success path.  There's a 'goto' right
>> before it.  Does this really fix your problem?
>>
> 
> The trick thing is. It do fix my problem on my centos 7 with gcc 8.3.1...
> 
> I am getting headache on this problem...

Checked again on my git tree. nothing weird, and code based on
cf7cd542d1b5 Add linux-next specific files for 20201104

Sorry, I have no idea where is the problem...


> 
>>> @@ -3339,7 +3339,8 @@ static bool swap_discardable(struct swap_info_struct *si)
>>>  	error = inode_drain_writes(inode);
>>>  	if (error) {
>>>  		inode->i_flags &= ~S_SWAPFILE;
>>> -		goto free_swap_address_space;
>>> +		exit_swap_address_space(p->type);
>>> +		goto bad_swap_unlock_inode;
>>>  	}
>>>  
>>>  	mutex_lock(&swapon_mutex);
>>> @@ -3364,8 +3365,6 @@ static bool swap_discardable(struct swap_info_struct *si)
>>>  
>>>  	error = 0;
>>>  	goto out;
>>> -free_swap_address_space:
>>> -	exit_swap_address_space(p->type);
>>>  bad_swap_unlock_inode:
>>>  	inode_unlock(inode);
>>>  bad_swap:
>>> -- 
>>> 1.8.3.1
>>>
>>>


  reply	other threads:[~2020-11-09 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 11:47 Alex Shi
2020-11-09 12:07 ` Matthew Wilcox
2020-11-09 12:17   ` Alex Shi
2020-11-09 12:36     ` Alex Shi [this message]
2020-11-09 12:07 linmiaohe

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=46e34498-01aa-3442-eee3-d3b84a00e1a8@linux.alibaba.com \
    --to=alex.shi@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=darrick.wong@oracle.com \
    --cc=hughd@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.org \
    /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