linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] hotfixes for 6.2
Date: Tue, 14 Feb 2023 09:26:03 +0800	[thread overview]
Message-ID: <dd2ba3b9-8fab-ce3b-4f01-eadbb527f3bc@linux.alibaba.com> (raw)
In-Reply-To: <CAHk-=wiBrY+O-4=2mrbVyxR+hOqfdJ=Do6xoucfJ9_5az01L4Q@mail.gmail.com>



On 2/14/2023 6:19 AM, Linus Torvalds wrote:
> On Mon, Feb 13, 2023 at 2:08 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> Kuan-Ying Lee (1):
>>        mm/gup: add folio to list when folio_isolate_lru() succeed
> 
> Ugh. I really hate fixes like this.
> 
> The problem came from mis-understanding the return value of
> folio_isolate_lru(), and thinking that it was a boolean
> success/failure thing.
> 
> It wasn't, it was an integer "success/errno" thing, and the sense of
> the test was wrong. So the patch is
> 
> -       if (!folio_isolate_lru(folio))
> +       if (folio_isolate_lru(folio))
>                  continue;
> 
> but at no point was the code *clarified*.
> 
> Wouldn't it have been much better to write the new code to be
> 
>          if (folio_isolate_lru(folio) < 0)
>                  continue;
> 
> to actually make it clear that this is a "negative error return check".
> 
> I've pulled this, but I really think that when somebody notices that
> we had a silly bug because of a misunderstanding like this, it's not
> just that the bug should be fixed, the code should also be *clarified*
> at the same time.

Yes, agree, I need to check the return value of folio_isolate_lru() 
every time when looking at the code. I can help to create a patch to 
make it clear for all users.


  reply	other threads:[~2023-02-14  1:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 22:08 [GIT PULL] hotfixes for 6.2 Andrew Morton
2023-02-13 22:19 ` Linus Torvalds
2023-02-14  1:26   ` Baolin Wang [this message]
2023-02-13 22:20 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-02-17 23:18 Andrew Morton
2023-02-18  3:04 ` pr-tracker-bot

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=dd2ba3b9-8fab-ce3b-4f01-eadbb527f3bc@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).