public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Ryan Roberts <ryan.roberts@arm.com>
Subject: Re: linux-next: Signed-off-bys missing for commit in the mm-hotfixes tree
Date: Sun, 24 Sep 2023 16:42:01 -0700	[thread overview]
Message-ID: <20230924164201.863ad5e63a2d555f6d33254c@linux-foundation.org> (raw)
In-Reply-To: <20230925075026.2a6b4e65@canb.auug.org.au>

On Mon, 25 Sep 2023 07:50:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> Commit
> 
>   48248e468270 ("mm: hugetlb: add huge page size param to set_huge_pte_at()")
> 
> is missing Signed-off-bys from its author and committer.
> 
> It looks like the commit message has been truncated.

Ah, thanks.  The changelog has a stray ^---$:

: If CONFIG_DEBUG_VM is enabled, we do at least get a BUG(), but otherwise,
: it will dereference a bad pointer in page_folio():
: 
:     static inline struct folio *hugetlb_swap_entry_to_folio(swp_entry_t entry)
:     {
:         VM_BUG_ON(!is_migration_entry(entry) && !is_hwpoison_entry(entry));
: 
:         return page_folio(pfn_to_page(swp_offset_pfn(entry)));
:     }
: 
: 
: Fix

<chomp>

: ---
: 
: The simplest fix would have been to revert the dodgy cleanup commit
: 18f3962953e4 ("mm: hugetlb: kill set_huge_swap_pte_at()"), but since
: things have moved on, this would have required an audit of all the new
: set_huge_pte_at() call sites to see if they should be converted to
: set_huge_swap_pte_at().  As per the original intent of the change, it
: would also leave us open to future bugs when people invariably get it
: wrong and call the wrong helper.

That's actually from the [0/n] intro, which I pasted into the [1/n]
changelog.

It gets through my scripts OK
(https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-hugetlb-add-huge-page-size-param-to-set_huge_pte_at.patch),
but it looks like git-quiltimport did the deed.

Let me add a check for that...

  reply	other threads:[~2023-09-24 23:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 21:50 linux-next: Signed-off-bys missing for commit in the mm-hotfixes tree Stephen Rothwell
2023-09-24 23:42 ` Andrew Morton [this message]
2023-09-25  8:58   ` Ryan Roberts
  -- strict thread matches above, loose matches on Subject: below --
2022-12-04 20:49 Stephen Rothwell
2022-12-04 22:02 ` Andrew Morton

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=20230924164201.863ad5e63a2d555f6d33254c@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=sfr@canb.auug.org.au \
    /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