LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@denx.de,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH 4.9 000/206] 4.9.291-rc2 review
Date: Thu, 25 Nov 2021 07:45:22 -0800	[thread overview]
Message-ID: <dd620210-af02-189c-f972-e31bd21008b4@roeck-us.net> (raw)
In-Reply-To: <20211125125641.226524689@linuxfoundation.org>

On 11/25/21 4:57 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.291 release.
> There are 206 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Sat, 27 Nov 2021 12:56:08 +0000.
> Anything received after that time might be too late.
> 

In file included from arch/sh/mm/init.c:25:
arch/sh/include/asm/tlb.h:118:15: error: return type defaults to 'int' [-Werror=return-type]
   118 | static inline tlb_flush_pmd_range(struct mmu_gather *tlb, unsigned long address,

The problem affects v4.9.y, v4.14.y, and v4.19.y.

Commit aca917cb287ba99c5 ("hugetlbfs: flush TLBs correctly after huge_pmd_unshare")
doesn't really match the upstream commit and obviously was not even build tested
on sh (and I would suspect it was not tested on other architectures either).
It seems to me that it may do more harm than good.

Guenter

  reply	other threads:[~2021-11-25 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 12:57 Greg Kroah-Hartman
2021-11-25 15:45 ` Guenter Roeck [this message]
2021-11-25 15:56   ` Greg Kroah-Hartman

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=dd620210-af02-189c-f972-e31bd21008b4@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=pavel@denx.de \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [PATCH 4.9 000/206] 4.9.291-rc2 review' \
    /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).