From: patchwork-bot+linux-riscv@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
richard.henderson@linaro.org, mattst88@gmail.com,
linmag7@gmail.com, linux@armlinux.org.uk,
catalin.marinas@arm.com, will@kernel.org, ardb@kernel.org,
chenhuacai@kernel.org, kernel@xen0n.name, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com, chleroy@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, davem@davemloft.net, andreas@gaisler.com,
richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net, tglx@kernel.org, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, herbert@gondor.apana.org.au,
dan.j.williams@intel.com, clm@fb.com, dsterba@suse.com,
arnd@arndb.de, song@kernel.org, yukuai@fnnas.com,
linan122@huawei.com, tytso@mit.edu, Jason@zx2c4.com,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org, linux-um@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-arch@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [PATCH 01/28] xor: assert that xor_blocks is not call from interrupt context
Date: Thu, 30 Apr 2026 03:24:59 +0000 [thread overview]
Message-ID: <177751949930.2274119.9590297379331785751.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260327061704.3707577-2-hch@lst.de>
Hello:
This series was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:
On Fri, 27 Mar 2026 07:16:33 +0100 you wrote:
> Most of the optimized xor_blocks versions require FPU/vector registers,
> which generally are not supported in interrupt context.
>
> Both callers already are in user context, so enforce this at the highest
> level.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> [...]
Here is the summary with links:
- [01/28] xor: assert that xor_blocks is not call from interrupt context
https://git.kernel.org/riscv/c/d8593b8f9354
- [02/28] arm/xor: remove in_interrupt() handling
https://git.kernel.org/riscv/c/b7ca705758b9
- [03/28] arm64/xor: fix conflicting attributes for xor_block_template
https://git.kernel.org/riscv/c/675a0dd596e7
- [04/28] um/xor: cleanup xor.h
https://git.kernel.org/riscv/c/3ea16a98518a
- [05/28] xor: move to lib/raid/
https://git.kernel.org/riscv/c/9e229025e247
- [06/28] xor: small cleanups
https://git.kernel.org/riscv/c/7c6e6b2b48e8
- [07/28] xor: cleanup registration and probing
https://git.kernel.org/riscv/c/0471415f3fd6
- [08/28] xor: split xor.h
https://git.kernel.org/riscv/c/54e20be48fd4
- [09/28] xor: remove macro abuse for XOR implementation registrations
https://git.kernel.org/riscv/c/35ebc4de1059
- [10/28] xor: move generic implementations out of asm-generic/xor.h
https://git.kernel.org/riscv/c/c46928fdcfa0
- [11/28] alpha: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/503793b1340e
- [12/28] arm: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/0d64a24ec0c0
- [13/28] arm64: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/3786f2ad0095
- [14/28] loongarch: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/033bee3e4963
- [15/28] powerpc: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/3f276cece4dd
- [16/28] riscv: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/5265d55b2146
- [17/28] sparc: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/7f96362396ee
- [18/28] s390: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/95c104cc5571
- [19/28] x86: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/77fd47e57a09
- [20/28] xor: avoid indirect calls for arm64-optimized ops
https://git.kernel.org/riscv/c/352ebd066b62
- [21/28] xor: make xor.ko self-contained in lib/raid/
https://git.kernel.org/riscv/c/e20043b4765c
- [22/28] xor: add a better public API
(no matching commit)
- [23/28] xor: add a better public API
(no matching commit)
- [24/28] async_xor: use xor_gen
https://git.kernel.org/riscv/c/7c12c32b9f73
- [25/28] btrfs: use xor_gen
https://git.kernel.org/riscv/c/0f629e7283ad
- [26/28] xor: pass the entire operation to the low-level ops
https://git.kernel.org/riscv/c/80dcf0a7832a
- [27/28] xor: use static_call for xor_gen
https://git.kernel.org/riscv/c/a21921dd02d3
- [28/28] xor: add a kunit test case
https://git.kernel.org/riscv/c/af53e85ef797
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
richard.henderson@linaro.org, mattst88@gmail.com,
linmag7@gmail.com, linux@armlinux.org.uk,
catalin.marinas@arm.com, will@kernel.org, ardb@kernel.org,
chenhuacai@kernel.org, kernel@xen0n.name, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com, chleroy@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, davem@davemloft.net, andreas@gaisler.com,
richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net, tglx@kernel.org, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, herbert@gondor.apana.org.au,
dan.j.williams@intel.com, clm@fb.com, dsterba@suse.com,
arnd@arndb.de, song@kernel.org, yukuai@fnnas.com,
linan122@huawei.com, tytso@mit.edu, Jason@zx2c4.com,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org, linux-um@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-arch@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [PATCH 01/28] xor: assert that xor_blocks is not call from interrupt context
Date: Thu, 30 Apr 2026 03:24:59 +0000 [thread overview]
Message-ID: <177751949930.2274119.9590297379331785751.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260327061704.3707577-2-hch@lst.de>
Hello:
This series was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:
On Fri, 27 Mar 2026 07:16:33 +0100 you wrote:
> Most of the optimized xor_blocks versions require FPU/vector registers,
> which generally are not supported in interrupt context.
>
> Both callers already are in user context, so enforce this at the highest
> level.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> [...]
Here is the summary with links:
- [01/28] xor: assert that xor_blocks is not call from interrupt context
https://git.kernel.org/riscv/c/d8593b8f9354
- [02/28] arm/xor: remove in_interrupt() handling
https://git.kernel.org/riscv/c/b7ca705758b9
- [03/28] arm64/xor: fix conflicting attributes for xor_block_template
https://git.kernel.org/riscv/c/675a0dd596e7
- [04/28] um/xor: cleanup xor.h
https://git.kernel.org/riscv/c/3ea16a98518a
- [05/28] xor: move to lib/raid/
https://git.kernel.org/riscv/c/9e229025e247
- [06/28] xor: small cleanups
https://git.kernel.org/riscv/c/7c6e6b2b48e8
- [07/28] xor: cleanup registration and probing
https://git.kernel.org/riscv/c/0471415f3fd6
- [08/28] xor: split xor.h
https://git.kernel.org/riscv/c/54e20be48fd4
- [09/28] xor: remove macro abuse for XOR implementation registrations
https://git.kernel.org/riscv/c/35ebc4de1059
- [10/28] xor: move generic implementations out of asm-generic/xor.h
https://git.kernel.org/riscv/c/c46928fdcfa0
- [11/28] alpha: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/503793b1340e
- [12/28] arm: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/0d64a24ec0c0
- [13/28] arm64: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/3786f2ad0095
- [14/28] loongarch: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/033bee3e4963
- [15/28] powerpc: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/3f276cece4dd
- [16/28] riscv: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/5265d55b2146
- [17/28] sparc: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/7f96362396ee
- [18/28] s390: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/95c104cc5571
- [19/28] x86: move the XOR code to lib/raid/
https://git.kernel.org/riscv/c/77fd47e57a09
- [20/28] xor: avoid indirect calls for arm64-optimized ops
https://git.kernel.org/riscv/c/352ebd066b62
- [21/28] xor: make xor.ko self-contained in lib/raid/
https://git.kernel.org/riscv/c/e20043b4765c
- [22/28] xor: add a better public API
(no matching commit)
- [23/28] xor: add a better public API
(no matching commit)
- [24/28] async_xor: use xor_gen
https://git.kernel.org/riscv/c/7c12c32b9f73
- [25/28] btrfs: use xor_gen
https://git.kernel.org/riscv/c/0f629e7283ad
- [26/28] xor: pass the entire operation to the low-level ops
https://git.kernel.org/riscv/c/80dcf0a7832a
- [27/28] xor: use static_call for xor_gen
https://git.kernel.org/riscv/c/a21921dd02d3
- [28/28] xor: add a kunit test case
https://git.kernel.org/riscv/c/af53e85ef797
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-04-30 3:25 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 6:16 cleanup the RAID5 XOR library v4 Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 01/28] xor: assert that xor_blocks is not call from interrupt context Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-04-30 3:24 ` patchwork-bot+linux-riscv [this message]
2026-04-30 3:24 ` patchwork-bot+linux-riscv
2026-03-27 6:16 ` [PATCH 02/28] arm/xor: remove in_interrupt() handling Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 03/28] arm64/xor: fix conflicting attributes for xor_block_template Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 8:25 ` Ard Biesheuvel
2026-03-27 8:25 ` Ard Biesheuvel
2026-03-27 6:16 ` [PATCH 04/28] um/xor: cleanup xor.h Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 05/28] xor: move to lib/raid/ Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 06/28] xor: small cleanups Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 07/28] xor: cleanup registration and probing Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 08/28] xor: split xor.h Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 09/28] xor: remove macro abuse for XOR implementation registrations Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 10/28] xor: move generic implementations out of asm-generic/xor.h Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 11/28] alpha: move the XOR code to lib/raid/ Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 12/28] arm: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 13/28] arm64: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 14/28] loongarch: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 15/28] powerpc: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 16/28] riscv: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 17/28] sparc: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 18/28] s390: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 19/28] x86: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 20/28] xor: avoid indirect calls for arm64-optimized ops Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 21/28] xor: make xor.ko self-contained in lib/raid/ Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 22/28] xor: add a better public API Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-04-10 3:03 ` Dan Williams
2026-04-10 3:03 ` Dan Williams
2026-03-27 6:16 ` [PATCH 23/28] " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 17:51 ` Andrew Morton
2026-03-27 17:51 ` Andrew Morton
2026-03-27 6:16 ` [PATCH 24/28] async_xor: use xor_gen Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-04-10 3:19 ` Dan Williams
2026-04-10 3:19 ` Dan Williams
2026-03-27 6:16 ` [PATCH 25/28] btrfs: " Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 26/28] xor: pass the entire operation to the low-level ops Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:16 ` [PATCH 27/28] xor: use static_call for xor_gen Christoph Hellwig
2026-03-27 6:16 ` Christoph Hellwig
2026-03-27 6:17 ` [PATCH 28/28] xor: add a kunit test case Christoph Hellwig
2026-03-27 6:17 ` Christoph Hellwig
2026-03-27 10:37 ` cleanup the RAID5 XOR library v4 Ard Biesheuvel
2026-03-27 10:37 ` Ard Biesheuvel
2026-03-27 17:49 ` Andrew Morton
2026-03-27 17:49 ` Andrew Morton
2026-03-29 21:31 ` Eric Biggers
2026-03-29 21:31 ` Eric Biggers
2026-03-29 22:51 ` Andrew Morton
2026-03-29 22:51 ` Andrew Morton
2026-03-30 4:07 ` Eric Biggers
2026-03-30 4:07 ` Eric Biggers
2026-03-30 5:26 ` Christoph Hellwig
2026-03-30 5:26 ` Christoph Hellwig
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=177751949930.2274119.9590297379331785751.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Jason@zx2c4.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=andreas@gaisler.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=chleroy@kernel.org \
--cc=clm@fb.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dsterba@suse.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=johannes@sipsolutions.net \
--cc=kernel@xen0n.name \
--cc=linan122@huawei.com \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=mattst88@gmail.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=richard.henderson@linaro.org \
--cc=richard@nod.at \
--cc=song@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=tytso@mit.edu \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yukuai@fnnas.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.