linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: simplify the VM_BUG_ON condition in pmdp_huge_clear_flush()
Date: Tue, 2 Feb 2021 10:09:59 +0800	[thread overview]
Message-ID: <2e2c1d42-9492-4e30-9646-bfa06b2d14d7@huawei.com> (raw)
In-Reply-To: <20210201153354.e640247cb5ab306e909322d0@linux-foundation.org>

Hi:
On 2021/2/2 7:33, Andrew Morton wrote:
> On Mon, 1 Feb 2021 06:43:19 -0500 Miaohe Lin <linmiaohe@huawei.com> wrote:
> 
>> The condition (A && !C && !D) || !A is equivalent to !A || (A && !C && !D)
>> and can be further simplified to !A || (!C && !D).
>>
>> ..
>>
>> --- a/mm/pgtable-generic.c
>> +++ b/mm/pgtable-generic.c
>> @@ -135,8 +135,8 @@ pmd_t pmdp_huge_clear_flush(struct vm_area_struct *vma, unsigned long address,
>>  {
>>  	pmd_t pmd;
>>  	VM_BUG_ON(address & ~HPAGE_PMD_MASK);
>> -	VM_BUG_ON((pmd_present(*pmdp) && !pmd_trans_huge(*pmdp) &&
>> -			   !pmd_devmap(*pmdp)) || !pmd_present(*pmdp));
>> +	VM_BUG_ON(!pmd_present(*pmdp) || (!pmd_trans_huge(*pmdp) &&
>> +					  !pmd_devmap(*pmdp)));
>>  	pmd = pmdp_huge_get_and_clear(vma->vm_mm, address, pmdp);
>>  	flush_pmd_tlb_range(vma, address, address + HPAGE_PMD_SIZE);
>>  	return pmd;
> 
> True, and the resulting code is still readable enough.
> 
> But a problem with such a complex expression is that the developer will
> have trouble figuring out why the BUG actually triggered.
> 

Agree! We can determine which condition is failing through the line number __but__
we can't figure out exactly which one triggered BUG for a complex expression.

> If we had a VM_BUG_ON_PMD() then we could print the pmd's value and
> permit diagnosis from that.  But we don't have such a thing.
> 
> So I suggest that it would be better to have
> 
> 	VM_BUG_ON((pmd_present(*pmdp) && !pmd_trans_huge(*pmdp) &&
> 			   !pmd_devmap(*pmdp)));
> 	VM_BUG_ON(!pmd_present(*pmdp));
> 
> This way, the BUG()'s file-n-line output will tell us more about why the
> kernel went splat.
> 
> 
> I suppose maybe this could be optimized the same way, as
> 
> 	VM_BUG_ON(!pmd_present(*pmdp));
> 	/* Below assumes pmd_present() is true */
> 	VM_BUG_ON(!pmd_trans_huge(*pmdp) && !pmd_devmap(*pmdp));

This one looks good and provide more information than before. I can send another patch to do this (and feel free to merge into
this one), should I ?

Many thanks.

> 
> Which works because VM_BUG_ON is, depending up Kconfig, either a no-op
> or a noreturn-if-it-triggered.  I'm not sure if I like this trick much though.
> 
> .
> 


      reply	other threads:[~2021-02-02  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 11:43 Miaohe Lin
2021-02-01 23:33 ` Andrew Morton
2021-02-02  2:09   ` Miaohe Lin [this message]

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=2e2c1d42-9492-4e30-9646-bfa06b2d14d7@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --subject='Re: [PATCH] mm: simplify the VM_BUG_ON condition in pmdp_huge_clear_flush()' \
    /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

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).