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, hagar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.11 000/249] 6.11.7-rc2 review
Date: Tue, 12 Nov 2024 09:33:04 +0100 [thread overview]
Message-ID: <2024111257-boogeyman-hatless-9872@gregkh> (raw)
In-Reply-To: <d440b33c-8634-46c2-8fb6-8ee4e7b43534@roeck-us.net>
On Sun, Nov 10, 2024 at 07:53:32AM -0800, Guenter Roeck wrote:
> On 11/6/24 22:47, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.11.7 release.
> > There are 249 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, 09 Nov 2024 06:45:18 +0000.
> > Anything received after that time might be too late.
> >
> [ ... ]
>
> > Naohiro Aota <naohiro.aota@wdc.com>
> > btrfs: fix error propagation of split bios
> >
>
> This patch triggers:
>
> ERROR: modpost: "__cmpxchg_called_with_bad_pointer" [fs/btrfs/btrfs.ko] undefined!
>
> or:
>
> fs/btrfs/bio.o: In function `btrfs_bio_alloc':
> fs/btrfs/bio.c:73: undefined reference to `__cmpxchg_called_with_bad_pointer'
> fs/btrfs/bio.o: In function `__cmpxchg':
> arch/xtensa/include/asm/cmpxchg.h:78: undefined reference to `__cmpxchg_called_with_bad_pointer'
>
> on xtensa builds with btrfs enabled.
>
> Upstream commit e799bef0d9c8 ("xtensa: Emulate one-byte cmpxchg") is
> required to fix the problem.
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2024-11-12 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 6:47 [PATCH 6.11 000/249] 6.11.7-rc2 review Greg Kroah-Hartman
2024-11-07 8:24 ` Luna Jernberg
2024-11-07 12:54 ` Pavel Machek
2024-11-07 13:28 ` Mark Brown
2024-11-07 14:28 ` Pavel Machek
2024-11-07 13:43 ` Jon Hunter
2024-11-07 14:26 ` Peter Schneider
2024-11-07 14:55 ` Mark Brown
2024-11-07 19:57 ` Florian Fainelli
2024-11-08 2:09 ` Ron Economos
2024-11-08 7:14 ` [PATCH 6.11] " Hardik Garg
2024-11-08 11:44 ` [PATCH 6.11 000/249] " Naresh Kamboju
2024-11-08 15:02 ` Muhammad Usama Anjum
2024-11-08 15:46 ` Justin Forbes
2024-11-08 15:58 ` Markus Reichelt
2024-11-10 15:53 ` Guenter Roeck
2024-11-12 8:33 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 16:44 Ronald Warsow
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=2024111257-boogeyman-hatless-9872@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hagar@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