public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, 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,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/389] 6.6.76-rc2 review
Date: Tue, 11 Feb 2025 09:34:37 +0100	[thread overview]
Message-ID: <2025021147-pacifier-richly-ce1e@gregkh> (raw)
In-Reply-To: <cd10a924-ae65-4b02-aea2-e629947ca7a3@roeck-us.net>

On Sun, Feb 09, 2025 at 07:19:33AM -0800, Guenter Roeck wrote:
> On 2/6/25 08:06, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.6.76 release.
> > There are 389 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, 08 Feb 2025 15:51:12 +0000.
> > Anything received after that time might be too late.
> > 
> [ ... ]
> 
> > Hongbo Li <lihongbo22@huawei.com>
> >      hostfs: fix the host directory parse when mounting.
> 
> This patch results in:
> 
> Building um:defconfig ... failed
> --------------
> Error log:
> fs/hostfs/hostfs_kern.c:972:9: error: implicit declaration of function 'fsparam_string_empty'; did you mean 'fsparam_string'? [-Werror=implicit-function-declaration]
>   972 |         fsparam_string_empty("hostfs",          Opt_hostfs),
> 
> because fsparam_string_empty() is not declared globally in v6.6.y.
> 
> The patch declaring it is 7b30851a70645 ("fs_parser: move fsparam_string_empty()
> helper into header"). Applying that patch on top of 6.6.76 fixes the problem.
> 
> The problem only affects "um" builds since hostfs (CONFIG_HOSTFS) is only available
> and used there. Oddly enough, the patch breaks the build of this file instead of
> fixing the problem it claims to fix, and it looks like no one noticed.
> On top of that, "hostfs: convert hostfs to use the new mount API" was obviously
> not tested. It looks like a substantial change which would definitely warrant
> testing when backported.
> 
> That makes me wonder: Should I stop build testing "um" images in older kernels ?

No, it's good for testing and I'm pretty sure that Android still uses it
for their test infrastructure so it matters.  I'll go do some reverts
now and push out a new release with this fixed as it's now shown up on
the kernel.ci build reports as well.

thanks for pointing it out.

greg k-h

      reply	other threads:[~2025-02-11  8:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 16:06 [PATCH 6.6 000/389] 6.6.76-rc2 review Greg Kroah-Hartman
2025-02-06 18:07 ` Florian Fainelli
2025-02-07 11:55 ` Jon Hunter
2025-02-07 11:59   ` Jon Hunter
2025-02-07 11:58 ` Jon Hunter
2025-02-07 19:37 ` Mark Brown
2025-02-07 23:17 ` [PATCH 6.6] " Hardik Garg
2025-02-08  2:13 ` [PATCH 6.6 000/389] " Peter Schneider
2025-02-08  5:25 ` Barry K. Nathan
2025-02-08  7:21   ` Greg Kroah-Hartman
2025-02-08 11:24 ` Naresh Kamboju
2025-02-17 11:30   ` Naresh Kamboju
2025-02-17 11:37     ` Greg Kroah-Hartman
2025-02-19 11:46       ` Naresh Kamboju
2025-02-19 12:13         ` Greg Kroah-Hartman
2025-02-19 14:00     ` Catalin Marinas
2025-02-19 15:43       ` Dan Carpenter
2025-02-19 15:52         ` Dan Carpenter
2025-02-19 15:52         ` Catalin Marinas
2025-02-19 17:18       ` Catalin Marinas
2025-02-19 18:09         ` Greg Kroah-Hartman
2025-02-19 19:16           ` Catalin Marinas
2025-02-19 18:31         ` Yang Shi
2025-02-09 15:19 ` Guenter Roeck
2025-02-11  8:34   ` Greg Kroah-Hartman [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=2025021147-pacifier-richly-ce1e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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