-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull one more powerpc fix for 5.17:
The following changes since commit 58dbe9b373df2828d873b1c0e5afc77485b2f376:
powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set
(2022-03-05 20:42:21 +1100)
are available
On Fri, 11 Mar 2022 15:26:42 +1100 Michael Ellerman wrote:
> > What will be the merge strategy ? I guess it's a bit late to get it
> > through powerpc tree, so I was just wondering whether we could get
> > patches 2 to 5 in mm this cycle, and the powerpc ones next cycle ?
>
> Yeah I didn't
On 3/11/22 15:15, Michael Ellerman wrote:
Fāng-ruì Sòng writes:
On Thu, Mar 10, 2022 at 11:48 AM Nick Desaulniers
wrote:
On Tue, Mar 8, 2022 at 9:53 PM Fangrui Song wrote:
DT_RELACOUNT is an ELF dynamic tag inherited from SunOS indicating the
number of R_*_RELATIVE relocations. It is
Christophe Leroy writes:
> Hi Michael, hi Andrew
>
> Le 09/03/2022 à 18:44, Christophe Leroy a écrit :
>> Rebased on top of powerpc/next branch
>>
>> This series converts powerpc to default topdown mmap layout.
>>
>> powerpc requires its own arch_get_unmapped_area() only when
>> slices are
Fāng-ruì Sòng writes:
> On Thu, Mar 10, 2022 at 11:48 AM Nick Desaulniers
> wrote:
>>
>> On Tue, Mar 8, 2022 at 9:53 PM Fangrui Song wrote:
>> >
>> > DT_RELACOUNT is an ELF dynamic tag inherited from SunOS indicating the
>> > number of R_*_RELATIVE relocations. It is optional but
On Fri, 2022-03-11 at 12:47 +1000, Nicholas Piggin wrote:
> Commit cf13435b730a ("powerpc/tm: Fix userspace r13 corruption") fixes
> a problem in treclaim where a SLB miss can occur on the
> thread_struct->ckpt_regs while SCRATCH0 is live with the saved user r13
> value, clobbering it with the
Currently the aer_irq() handler returns IRQ_NONE for cases without bits
PCI_ERR_ROOT_UNCOR_RCV or PCI_ERR_ROOT_COR_RCV are set. But this
assumption is incorrect.
Consider a scenario where aer_irq() is triggered for a correctable
error, and while we process the error and before we clear the error
Commit cf13435b730a ("powerpc/tm: Fix userspace r13 corruption") fixes
a problem in treclaim where a SLB miss can occur on the
thread_struct->ckpt_regs while SCRATCH0 is live with the saved user r13
value, clobbering it with the kernel r13 and ultimately resulting in
kernel r13 being stored in
Hi Arnd,
On Mon, Feb 28, 2022 at 12:30 AM wrote:
>
> From: Guo Ren
>
> If the current task is in COMPAT mode, set SR_UXL_32 in status for
> returning userspace. We need CONFIG _COMPAT to prevent compiling
> errors with rv32 defconfig.
>
> Signed-off-by: Guo Ren
> Signed-off-by: Guo Ren
> Cc:
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 71941773e143369a73c9c4a3b62fbb60736a1182 Add linux-next specific
files for 20220310
Error/Warning reports:
https://lore.kernel.org/linux-doc/202202240704.pqd40a9l-...@intel.com
https
From: Ira Weiny
The WARN_ON check in arch_set_user_pkey_access() in the x86 architecture
fails to check for an invalid negative value.
A simple check for less than 0 would fix this issue however, in the call
stack below arch_set_user_pkey_access() the pkey should never be
negative on any
From: Ira Weiny
The number of pkeys supported on x86 and powerpc are much smaller than a
u16 value can hold. It is desirable to standardize on the type for
pkeys. powerpc currently supports the most pkeys at 32. u8 is plenty
large for that.
Standardize on the pkey types by changing u16 to
From: Ira Weiny
Negative values passed to pkeyshift() will cause an overflow of the amr
and imar values. Pkey should not be negative in this call path and u8
is large enough for the 32 pkeys available on powerpc.
Change pkey to u8 in init_amr() and init_iamr().
To: Michael Ellerman
Cc:
From: Ira Weiny
In the x86 code __arch_set_user_pkey_access() is not used and is not
defined.
Remove the dead declaration.
To: Dave Hansen
Signed-off-by: Ira Weiny
---
Changes from V1:
Make this part of a series of pkey clean ups
---
arch/x86/include/asm/pkeys.h | 6 --
1 file
From: Ira Weiny
I'm looking for acks that this is acceptable for official submission to the
maintainers. I believe the code to be better than RFC quality but I realize
that the type changes may be more churn than is desired.
The following patches contain pkey cleanups and an attempt to
From: Ira Weiny
arch_set_user_pkey_access() was declared two times in the header.
Remove the 2nd declaration.
Suggested-by: "Edgecombe, Rick P"
Signed-off-by: Ira Weiny
---
arch/x86/include/asm/pkeys.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/include/asm/pkeys.h
cbs=4 rcutorture.stat_interval=15
> > rcutorture.shutdown_secs=1800 rcutorture.test_no_idle_hz=1
> > rcutorture.verbose=1"
> >
> > The console.log is uploaded to:
> > http://154.223.142.244/logs/20220310/console.paul.log
> > The log tells us it is illegal inst
On Mon, Mar 07, 2022 at 11:10:40AM -0300, Alifer Moraes wrote:
> From: Pierluigi Passaro
>
> The platform_data structure is not populated when using device trees.
> This patch adds optional dts properties to allow populating it:
> - gpio-cfg
> - mic-cfg
> - num-drc-cfgs
> - drc-cfg-regs
> -
On Thu, Mar 10, 2022 at 06:09:51PM +, Christophe Leroy wrote:
>
>
> Le 10/03/2022 à 17:52, Bjorn Helgaas a écrit :
> > On Wed, Mar 09, 2022 at 06:44:35PM +0100, Christophe Leroy wrote:
> >> Today drivers/pci/controller/pci-xgene.c defines SZ_1T
> >>
> >> Move it into linux/sizes.h so that it
On 10.03.22 13:22, Thorsten Leemhuis wrote:
> On 10.03.22 12:22, Christophe Leroy wrote:
>> Le 10/03/2022 à 11:39, Thorsten Leemhuis a écrit :
>>> Hi, this is your Linux kernel regression tracker.
>>>
>>> I noticed a regression report in bugzilla.kernel.org that afaics nobody
>>> acted upon since
Le 10/03/2022 à 17:52, Bjorn Helgaas a écrit :
> On Wed, Mar 09, 2022 at 06:44:35PM +0100, Christophe Leroy wrote:
>> Today drivers/pci/controller/pci-xgene.c defines SZ_1T
>>
>> Move it into linux/sizes.h so that it can be re-used elsewhere.
>>
>> Link:
>>
On Wed, Mar 09, 2022 at 06:44:35PM +0100, Christophe Leroy wrote:
> Today drivers/pci/controller/pci-xgene.c defines SZ_1T
>
> Move it into linux/sizes.h so that it can be re-used elsewhere.
>
> Link:
>
On 09/03/2022, 16:51:04, Christophe Leroy wrote:
>
>
> Le 03/11/2020 à 18:13, Laurent Dufour a écrit :
>> The check introduced by the commit 83d3f0e90c6c ("powerpc/mm: tracking vDSO
>> remap") is wrong and is missing some partial unmaps of the VDSO.
>>
>> To be complete the check needs the base
https://bugzilla.kernel.org/show_bug.cgi?id=215652
--- Comment #9 from Alex Deucher (alexdeuc...@gmail.com) ---
Only the person that filed the bug can close it. If it's fixed for you, please
close it. Thanks!
--
You may reply to this email to add a comment.
You are receiving this mail
On Wed, Mar 09, 2022 at 08:05:21PM +0100, Lukas Wunner wrote:
> On Mon, Mar 07, 2022 at 11:48:01AM +0200, Ilpo Järvinen wrote:
> > On Sun, 6 Mar 2022, Lukas Wunner wrote:
> > > On Wed, Mar 02, 2022 at 11:56:05AM +0200, Ilpo Järvinen wrote:
> > > > This change is necessary for supporting devices
https://bugzilla.kernel.org/show_bug.cgi?id=215658
Erhard F. (erhar...@mailbox.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=215652
--- Comment #8 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 300550
--> https://bugzilla.kernel.org/attachment.cgi?id=300550=edit
kernel dmesg (kernel 5.17-rc7, CONFIG_DRM_RADEON=m, Talos II)
Seems this is issue already fixed in
On Thu, 10 Mar 2022 09:19:02 +, Wang Wensheng wrote:
> Fix to return a negative error code from the error handling case instead
> of 0, as done elsewhere in this function.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC:
On Wed, 9 Mar 2022, Lukas Wunner wrote:
> On Mon, Mar 07, 2022 at 11:48:01AM +0200, Ilpo Järvinen wrote:
> > On Sun, 6 Mar 2022, Lukas Wunner wrote:
> > > On Wed, Mar 02, 2022 at 11:56:05AM +0200, Ilpo Järvinen wrote:
> > > > This change is necessary for supporting devices with RS485
> > > >
On 3/10/22 17:41, Michael Ellerman wrote:
> Christophe Leroy writes:
>> Le 27/01/2022 à 08:20, Kajol Jain a écrit :
>>> From: Athira Rajeev
>>>
>>> The testcase uses event code "0x134001c040" to verify
>>> the settings for different fields in Monitor Mode Control
>>> Register 1 (MMCR1).
On 10.03.22 12:22, Christophe Leroy wrote:
> Le 10/03/2022 à 11:39, Thorsten Leemhuis a écrit :
>> Hi, this is your Linux kernel regression tracker.
>>
>> I noticed a regression report in bugzilla.kernel.org that afaics nobody
>> acted upon since it was reported about a week ago, that's why I
Christophe Leroy writes:
> Le 27/01/2022 à 08:20, Kajol Jain a écrit :
>> From: Athira Rajeev
>>
>> The testcase uses event code "0x134001c040" to verify
>> the settings for different fields in Monitor Mode Control
>> Register 1 (MMCR1). The fields include PMCxSEL, PMCXCOMB
>> PMCxUNIT,
https://bugzilla.kernel.org/show_bug.cgi?id=215658
Christophe Leroy (christophe.le...@csgroup.eu) changed:
What|Removed |Added
CC|
Hi,
Le 10/03/2022 à 11:39, Thorsten Leemhuis a écrit :
> Hi, this is your Linux kernel regression tracker.
>
> I noticed a regression report in bugzilla.kernel.org that afaics nobody
> acted upon since it was reported about a week ago, that's why I decided
> to forward it to the lists and a few
Hi, this is your Linux kernel regression tracker.
I noticed a regression report in bugzilla.kernel.org that afaics nobody
acted upon since it was reported about a week ago, that's why I decided
to forward it to the lists and a few relevant people to the CC. To quote
from the ticket:
> 5.16.12
Hi Palmer & Arnd
Seems we need a more strict check to distinguish ELFCLASS32/64 RISC in
elf for the elf_check_arch & compat_elf_check_arch. SET_PERSONALITY is
not enough.
diff --git a/arch/riscv/include/asm/elf.h b/arch/riscv/include/asm/elf.h
index d87d3bcc758d..2fcd854fb516 100644
---
Le 02/09/2020 à 05:51, Oliver O'Halloran a écrit :
The MPS field in the VF config space is marked as reserved in current
versions of the SR-IOV spec. In other words, this fixup doesn't do
anything.
Signed-off-by: Oliver O'Halloran
A lot of cleanup patches from Oliver were merged in
Le 13/07/2021 à 02:25, Krzysztof Wilczyński a écrit :
The pcie_reset_state_t type has been introduced in the commit
f7bdd12d234d ("pci: New PCI-E reset API") along with the enum
pcie_reset_state, but it has never been used for anything else
other than to define the members of the enumeration
al=15
rcutorture.shutdown_secs=1800 rcutorture.test_no_idle_hz=1
rcutorture.verbose=1"
The console.log is uploaded to:
http://154.223.142.244/logs/20220310/console.paul.log
The log tells us it is illegal instruction that causes the trouble:
[4.246387][T1] init[1]: illegal instruction (4) a
39 matches
Mail list logo
