public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, 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,
	Pavel Begunkov <asml.silence@gmail.com>,
	Anders Roxell <anders.roxell@linaro.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	io-uring@vger.kernel.org
Subject: Re: [PATCH 6.6 000/166] 6.6.84-rc1 review
Date: Thu, 20 Mar 2025 06:22:40 -0700	[thread overview]
Message-ID: <2025032031-negative-wreckage-dedf@gregkh> (raw)
In-Reply-To: <412b08d9-17fc-4a62-afd3-7371cf479f2d@kernel.dk>

On Thu, Mar 20, 2025 at 07:02:23AM -0600, Jens Axboe wrote:
> On 3/20/25 6:55 AM, Jens Axboe wrote:
> > On 3/19/25 5:51 PM, Greg Kroah-Hartman wrote:
> >> On Wed, Mar 19, 2025 at 10:37:20AM -0600, Jens Axboe wrote:
> >>> On 3/19/25 10:33 AM, Naresh Kamboju wrote:
> >>>> On Wed, 19 Mar 2025 at 20:09, Greg Kroah-Hartman
> >>>> <gregkh@linuxfoundation.org> wrote:
> >>>>>
> >>>>> This is the start of the stable review cycle for the 6.6.84 release.
> >>>>> There are 166 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 Fri, 21 Mar 2025 14:29:55 +0000.
> >>>>> Anything received after that time might be too late.
> >>>>>
> >>>>> The whole patch series can be found in one patch at:
> >>>>>         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.84-rc1.gz
> >>>>> or in the git tree and branch at:
> >>>>>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
> >>>>> and the diffstat can be found below.
> >>>>>
> >>>>> thanks,
> >>>>>
> >>>>> greg k-h
> >>>>
> >>>> Regressions on mips the rt305x_defconfig builds failed with gcc-12
> >>>> the stable-rc v6.6.83-167-gd16a828e7b09
> >>>>
> >>>> First seen on the v6.6.83-167-gd16a828e7b09
> >>>>  Good: v6.6.83
> >>>>  Bad: v6.6.83-167-gd16a828e7b09
> >>>>
> >>>> * mips, build
> >>>>   - gcc-12-rt305x_defconfig
> >>>>
> >>>> Regression Analysis:
> >>>>  - New regression? Yes
> >>>>  - Reproducibility? Yes
> >>>>
> >>>> Build regression: mips implicit declaration of function 'vunmap'
> >>>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >>>
> >>> Ah that's my fault, forgot to include the backport of:
> >>>
> >>> commit 62346c6cb28b043f2a6e95337d9081ec0b37b5f5
> >>> Author: Jens Axboe <axboe@kernel.dk>
> >>> Date:   Sat Mar 16 07:21:43 2024 -0600
> >>>
> >>>     mm: add nommu variant of vm_insert_pages()
> >>>
> >>> for 6.1-stable and 6.6-stable. Greg, can you just cherry pick that one?
> >>> It'll pick cleanly into both, should go before the io_uring mmap series
> >>> obviously.
> >>>
> >>> Sorry about that! I did have it in my local trees, but for some reason
> >>> forgot to include it in the sent in series.
> >>
> >> Wait, this is already in the 6.6.y and 6.1.y queues, so this can't be
> >> the fix.  Was there a fixup for that commit somewhere else that I'm
> >> missing?
> > 
> > Huh indeed, guess I didn't mess up in the first place. What is going on
> > here indeed... Is that mips config NOMMU yet doesn't link in mm/nommu.o?
> > 
> > Checking, and no, it definitely has MMU=y in the config. Guess I
> > should've read the initial report more closely, it's simply missing the
> > vunmap definition. Adding linux/vmalloc.h to io_uring/io_uring.c should
> > fix it.
> > 
> > How do we want to deal with this?
> 
> Either fold in the hunk from the previous email, or replace patch 2 in
> the series I sent with this one instead, which adds the vmalloc.h
> include. That should sort out the issue without needing add-on patches
> that don't exist upstream.

Now replaced, thanks!

      reply	other threads:[~2025-03-20 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250319143019.983527953@linuxfoundation.org>
2025-03-19 16:33 ` [PATCH 6.6 000/166] 6.6.84-rc1 review Naresh Kamboju
2025-03-19 16:37   ` Jens Axboe
2025-03-19 17:02     ` Greg Kroah-Hartman
2025-03-19 23:51     ` Greg Kroah-Hartman
2025-03-20 12:55       ` Jens Axboe
2025-03-20 13:02         ` Jens Axboe
2025-03-20 13:22           ` 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=2025032031-negative-wreckage-dedf@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=io-uring@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@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