6.1.103-rc1 review
Subsystems (3)
Greg Kroah-Hartman
maintainerPATCH 430/440 spi: spidev: order compatibles alphabetically
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
[ Upstream commit be5852457b7e85ad13b1bded9c97bed5ee1715a3 ]
Bring some order to reduce possibilities of conflicts.
Stable-dep-of: fc28d1c1fe3b ("spi: spidev: add correct compatible for Rohm BH2228FV")
--- drivers/spi/spidev.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/spi/spidev.c +4 -4
@@ -719,14 +719,14 @@ static int spidev_of_check(struct device *dev) }static const struct of_device_id spidev_dt_ids[] = { - { .compatible ="rohm,dh2228fv" , .data = &spidev_of_check }, + { .compatible ="cisco,spi-petra" , .data = &spidev_of_check }, + { .compatible ="dh,dhcom-board" , .data = &spidev_of_check }, { .compatible ="lineartechnology,ltc2488" , .data = &spidev_of_check }, - { .compatible ="semtech,sx1301" , .data = &spidev_of_check }, { .compatible ="lwn,bk4" , .data = &spidev_of_check }, - { .compatible ="dh,dhcom-board" , .data = &spidev_of_check }, { .compatible ="menlo,m53cpld" , .data = &spidev_of_check }, - { .compatible ="cisco,spi-petra" , .data = &spidev_of_check }, { .compatible ="micron,spi-authenta" , .data = &spidev_of_check }, + { .compatible ="rohm,dh2228fv" , .data = &spidev_of_check }, + { .compatible ="semtech,sx1301" , .data = &spidev_of_check }, { .compatible ="silabs,em3581" , .data = &spidev_of_check }, {}, };
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 431/440 spi: spidev: add correct compatible for Rohm BH2228FV
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Conor Dooley <[email protected]>
[ Upstream commit fc28d1c1fe3b3e2fbc50834c8f73dda72f6af9fc ]
When Maxime originally added the BH2228FV to the spidev driver, he spelt it incorrectly - the d should have been a b. Add the correctly spelt compatible to the driver. Although the majority of users of this compatible are abusers, there is at least one board that validly uses the incorrect spelt compatible, so keep it in the driver to avoid breaking the few real users it has.
--- drivers/spi/spidev.c | 1 + 1 file changed, 1 insertion(+)
drivers/spi/spidev.c +1 -0
@@ -725,6 +725,7 @@ static const struct of_device_id spidev_dt_ids[] = { { .compatible = "lwn,bk4", .data = &spidev_of_check }, { .compatible = "menlo,m53cpld", .data = &spidev_of_check }, { .compatible = "micron,spi-authenta", .data = &spidev_of_check }, + { .compatible = "rohm,bh2228fv", .data = &spidev_of_check }, { .compatible = "rohm,dh2228fv", .data = &spidev_of_check }, { .compatible = "semtech,sx1301", .data = &spidev_of_check }, { .compatible = "silabs,em3581", .data = &spidev_of_check },
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 432/440 ASoC: Intel: use soc_intel_is_byt_cr() only when IOSF_MBI is reachable
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pierre-Louis Bossart <[email protected]>
[ Upstream commit 9931f7d5d251882a147cc5811060097df43e79f5 ]
the Intel kbuild bot reports a link failure when IOSF_MBI is built-in but the Merrifield driver is configured as a module. The soc-intel-quirks.h is included for Merrifield platforms, but IOSF_MBI is not selected for that platform.
ld.lld: error: undefined symbol: iosf_mbi_read
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
referenced by
atom.c
sound/soc/sof/intel/atom.o:(atom_machine_select) in archive vmlinux.a
This patch forces the use of the fallback static inline when IOSF_MBI is not reachable.
--- sound/soc/intel/common/soc-intel-quirks.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/intel/common/soc-intel-quirks.h +1 -1
@@ -11,7 +11,7 @@#include <linux/platform_data/x86/soc.h> -#if IS_ENABLED (CONFIG_X86 ) +#if IS_REACHABLE (CONFIG_IOSF_MBI )#include <linux/dmi.h> #include <asm/iosf_mbi.h>
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 433/440 ceph: fix incorrect kmalloc size of pagevec mempool
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: ethanwu <[email protected]>
[ Upstream commit 03230edb0bd831662a7c08b6fef66b2a9a817774 ]
The kmalloc size of pagevec mempool is incorrectly calculated.
It misses the size of page pointer and only accounts the number for the array.
--- fs/ceph/super.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/ceph/super.c +2 -1
@@ -924,7 +924,8 @@ static int __init init_caches(void)if (!ceph_mds_request_cachep) goto bad_mds_req; - ceph_wb_pagevec_pool =mempool_create_kmalloc_pool (10 ,CEPH_MAX_WRITE_SIZE >>PAGE_SHIFT ); + ceph_wb_pagevec_pool =mempool_create_kmalloc_pool (10 , + (CEPH_MAX_WRITE_SIZE >>PAGE_SHIFT ) *sizeof (struct page *));if (!ceph_wb_pagevec_pool) goto bad_pagevec_pool;
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 434/440 s390/pci: Refactor arch_setup_msi_irqs()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gerd Bayer <[email protected]>
[ Upstream commit 5fd11b96b43708f2f6e3964412c301c1bd20ec0f ]
Factor out adapter interrupt allocation from arch_setup_msi_irqs() in preparation for enabling registration of multiple MSIs. Code movement only, no change of functionality intended.
Stable-dep-of: ab42fcb511fd ("s390/pci: Allow allocation of more than 1 MSI interrupt")
--- arch/s390/pci/pci_irq.c | 54 ++++++++++++++++++++++++----------------- 1 file changed, 32 insertions(+), 22 deletions(-)
arch/s390/pci/pci_irq.c +32 -22
@@ -268,33 +268,20 @@ static void zpci_floating_irq_handler(struct airq_struct *airq, } } -int arch_setup_msi_irqs (struct pci_dev *pdev,int nvec,int type) +static int __alloc_airq (struct zpci_dev *zdev,int msi_vecs, +unsigned long *bit) { -struct zpci_dev *zdev =to_zpci (pdev); -unsigned int hwirq, msi_vecs, cpu; -unsigned long bit; -struct msi_desc *msi; -struct msi_msg msg; -int cpu_addr; -int rc, irq; - - zdev->aisb =-1UL ; - zdev->msi_first_bit =-1U ; -if (type ==PCI_CAP_ID_MSI && nvec >1 ) -return 1 ; - msi_vecs = min_t(unsigned int, nvec, zdev->max_msi); -if (irq_delivery ==DIRECTED ) {/* Allocate cpu vector bits */ - bit =airq_iv_alloc (zpci_ibv[0 ], msi_vecs); -if (bit ==-1UL ) + *bit =airq_iv_alloc (zpci_ibv[0 ], msi_vecs); +if (*bit ==-1UL )return -EIO ; }else {/* Allocate adapter summary indicator bit */ - bit =airq_iv_alloc_bit (zpci_sbv); -if (bit ==-1UL ) + *bit =airq_iv_alloc_bit (zpci_sbv); +if (*bit ==-1UL )return -EIO ; - zdev->aisb = bit; + zdev->aisb = *bit;/* Create adapter interrupt vector */ zdev->aibv =airq_iv_create (msi_vecs,AIRQ_IV_DATA |AIRQ_IV_BITLOCK ,NULL );
@@ -302,10 +289,33 @@ int arch_setup_msi_irqs(struct pci_dev *pdev, int nvec, int type)return -ENOMEM ;/* Wire up shortcut pointer */ - zpci_ibv[bit] = zdev->aibv; + zpci_ibv[*bit] = zdev->aibv;/* Each function has its own interrupt vector */ - bit =0 ; + *bit =0 ; } +return 0 ; +} + +int arch_setup_msi_irqs (struct pci_dev *pdev,int nvec,int type) +{ +struct zpci_dev *zdev =to_zpci (pdev); +unsigned int hwirq, msi_vecs, cpu; +struct msi_desc *msi; +struct msi_msg msg; +unsigned long bit; +int cpu_addr; +int rc, irq; + + zdev->aisb =-1UL ; + zdev->msi_first_bit =-1U ; + +if (type ==PCI_CAP_ID_MSI && nvec >1 ) +return 1 ; + msi_vecs = min_t(unsigned int, nvec, zdev->max_msi); + + rc =__alloc_airq (zdev, msi_vecs, &bit); +if (rc <0 ) +return rc;/* Request MSI interrupts */ hwirq = bit;
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 435/440 s390/pci: Allow allocation of more than 1 MSI interrupt
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gerd Bayer <[email protected]>
[ Upstream commit ab42fcb511fd9d241bbab7cc3ca04e34e9fc0666 ]
On a PCI adapter that provides up to 8 MSI interrupt sources the s390 implementation of PCI interrupts rejected to accommodate them, although the underlying hardware is able to support that.
For MSI-X it is sufficient to allocate a single irq_desc per msi_desc, but for MSI multiple irq descriptors are attached to and controlled by a single msi descriptor. Add the appropriate loops to maintain multiple irq descriptors and tie/untie them to/from the appropriate AIBV bit, if a device driver allocates more than 1 MSI interrupt.
Common PCI code passes on requests to allocate a number of interrupt vectors based on the device drivers' demand and the PCI functions' capabilities. However, the root-complex of s390 systems support just a limited number of interrupt vectors per PCI function. Produce a kernel log message to inform about any architecture-specific capping that might be done.
With this change, we had a PCI adapter successfully raising interrupts to its device driver via all 8 sources.
--- arch/s390/pci/pci_irq.c | 62 ++++++++++++++++++++++++++++------------- 1 file changed, 42 insertions(+), 20 deletions(-)
arch/s390/pci/pci_irq.c +42 -20
@@ -298,8 +298,8 @@ static int __alloc_airq(struct zpci_dev *zdev, int msi_vecs,int arch_setup_msi_irqs (struct pci_dev *pdev,int nvec,int type) { +unsigned int hwirq, msi_vecs, irqs_per_msi, i, cpu;struct zpci_dev *zdev =to_zpci (pdev); -unsigned int hwirq, msi_vecs, cpu;struct msi_desc *msi;struct msi_msg msg;unsigned long bit;
@@ -309,30 +309,46 @@ int arch_setup_msi_irqs(struct pci_dev *pdev, int nvec, int type) zdev->aisb =-1UL ; zdev->msi_first_bit =-1U ; -if (type ==PCI_CAP_ID_MSI && nvec >1 ) -return 1 ; msi_vecs = min_t(unsigned int, nvec, zdev->max_msi); +if (msi_vecs < nvec) { +pr_info ("%s requested %d irqs, allocate system limit of %d" , +pci_name (pdev), nvec, zdev->max_msi); + } rc =__alloc_airq (zdev, msi_vecs, &bit);if (rc <0 )return rc; -/* Request MSI interrupts */ +/* +* Request MSI interrupts: +* When using MSI, nvec_used interrupt sources and their irq +* descriptors are controlled through one msi descriptor. +* Thus the outer loop over msi descriptors shall run only once, +* while two inner loops iterate over the interrupt vectors. +* When using MSI-X, each interrupt vector/irq descriptor +* is bound to exactly one msi descriptor (nvec_used is one). +* So the inner loops are executed once, while the outer iterates +* over the MSI-X descriptors. +*/ hwirq = bit;msi_for_each_desc (msi, &pdev->dev,MSI_DESC_NOTASSOCIATED ) { - rc = -EIO ;if (hwirq - bit >= msi_vecs)break ; - irq =__irq_alloc_descs (-1 ,0 ,1 ,0 ,THIS_MODULE , - (irq_delivery ==DIRECTED ) ? - msi->affinity :NULL ); + irqs_per_msi = min_t(unsigned int, msi_vecs, msi->nvec_used); + irq =__irq_alloc_descs (-1 ,0 , irqs_per_msi,0 ,THIS_MODULE , + (irq_delivery ==DIRECTED ) ? + msi->affinity :NULL );if (irq <0 )return -ENOMEM ; - rc =irq_set_msi_desc (irq, msi); -if (rc) -return rc; -irq_set_chip_and_handler (irq, &zpci_irq_chip, - handle_percpu_irq); + +for (i =0 ; i < irqs_per_msi; i++) { + rc =irq_set_msi_desc_off (irq, i, msi); +if (rc) +return rc; +irq_set_chip_and_handler (irq + i, &zpci_irq_chip, + handle_percpu_irq); + } + msg.data = hwirq - bit;if (irq_delivery ==DIRECTED ) {if (msi->affinity)
@@ -345,31 +361,35 @@ int arch_setup_msi_irqs(struct pci_dev *pdev, int nvec, int type) msg.address_lo |= (cpu_addr <<8 );for_each_possible_cpu (cpu) { -airq_iv_set_data (zpci_ibv[cpu], hwirq, irq); +for (i =0 ; i < irqs_per_msi; i++) +airq_iv_set_data (zpci_ibv[cpu], + hwirq + i, irq + i); } }else { msg.address_lo = zdev->msi_addr &0xffffffff ; -airq_iv_set_data (zdev->aibv, hwirq, irq); +for (i =0 ; i < irqs_per_msi; i++) +airq_iv_set_data (zdev->aibv, hwirq + i, irq + i); } msg.address_hi = zdev->msi_addr >>32 ;pci_write_msi_msg (irq, &msg); - hwirq++; + hwirq += irqs_per_msi; } zdev->msi_first_bit = bit; - zdev->msi_nr_irqs = msi_vecs; + zdev->msi_nr_irqs = hwirq - bit; rc =zpci_set_irq (zdev);if (rc)return rc; -return (msi_vecs == nvec) ?0 : msi_vecs; +return (zdev->msi_nr_irqs == nvec) ?0 : zdev->msi_nr_irqs; }void arch_teardown_msi_irqs (struct pci_dev *pdev) {struct zpci_dev *zdev =to_zpci (pdev);struct msi_desc *msi; +unsigned int i;int rc;/* Disable interrupts */
@@ -379,8 +399,10 @@ void arch_teardown_msi_irqs(struct pci_dev *pdev)/* Release MSI interrupts */ msi_for_each_desc (msi, &pdev->dev,MSI_DESC_ASSOCIATED ) { -irq_set_msi_desc (msi->irq,NULL ); -irq_free_desc (msi->irq); +for (i =0 ; i < msi->nvec_used; i++) { +irq_set_msi_desc (msi->irq + i,NULL ); +irq_free_desc (msi->irq + i); + } msi->msg.address_lo =0 ; msi->msg.address_hi =0 ; msi->msg.data =0 ;
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 436/440 s390/cpum_cf: Fix endless loop in CF_DIAG event stop
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Richter <[email protected]>
[ Upstream commit e6ce1f12d777f6ee22b20e10ae6a771e7e6f44f5 ]
Event CF_DIAG reads out complete counter sets using stcctm instruction. This is done at event start time when the process starts execution and at event stop time when the process is removed from the CPU. During removal the difference of each counter in the counter sets is calculated and saved as raw data in the ring buffer. This works fine unless the number of counters in a counter set is zero. This may happen for the extended counter set. This set is machine specific and the size of the counter set can be zero even when extended counter set is authorized for read access.
This case is not handled. cfdiag_diffctr() checks authorization of the extended counter set. If true the functions assumes the extended counter set has been saved in a data buffer. However this is not the case, cfdiag_getctrset() does not save a counter set with counter set size of zero. This mismatch causes an endless loop in the counter set readout during event stop handling.
The calculation of the difference of the counters in each counter now verifies the size of the counter set is non-zero. A counter set with size zero is skipped.
--- arch/s390/kernel/perf_cpum_cf.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
arch/s390/kernel/perf_cpum_cf.c +10 -4
@@ -213,25 +213,31 @@ static int cfdiag_diffctr(struct cpu_cf_events *cpuhw, unsigned long auth)struct cf_trailer_entry *trailer_start, *trailer_stop;struct cf_ctrset_entry *ctrstart, *ctrstop;size_t offset =0 ; +int i; - auth &= (1 <<CPUMF_LCCTL_ENABLE_SHIFT ) -1 ; -do { +for (i =CPUMF_CTR_SET_BASIC ; i <CPUMF_CTR_SET_MAX ; ++i) { ctrstart = (struct cf_ctrset_entry *)(cpuhw->start + offset); ctrstop = (struct cf_ctrset_entry *)(cpuhw->stop + offset); +/* Counter set not authorized */ +if (!(auth & cpumf_ctr_ctl[i])) +continue ; +/* Counter set size zero was not saved */ +if (!cpum_cf_read_setsize (i)) +continue ; +if (memcmp (ctrstop, ctrstart,sizeof (*ctrstop))) {pr_err_once ("cpum_cf_diag counter set compare error " "in set %i\n" , ctrstart->set);return 0 ; } - auth &= ~cpumf_ctr_ctl[ctrstart->set];if (ctrstart->def ==CF_DIAG_CTRSET_DEF ) {cfdiag_diffctrset ((u64 *)(ctrstart +1 ), (u64 *)(ctrstop +1 ), ctrstart->ctr); offset += ctrstart->ctr *sizeof (u64) +sizeof (*ctrstart); } - }while (ctrstart->def && auth); + }/* Save time_stamp from start of event in stop's trailer */ trailer_start = (struct cf_trailer_entry *)(cpuhw->start + offset);
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 437/440 iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Artem Chernyshev <[email protected]>
[ Upstream commit 630482ee0653decf9e2482ac6181897eb6cde5b8 ]
In sprd_iommu_cleanup() before calling function sprd_iommu_hw_en() dom->sdev is equal to NULL, which leads to null dereference.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
--- drivers/iommu/sprd-iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iommu/sprd-iommu.c +1 -1
@@ -234,8 +234,8 @@ static void sprd_iommu_cleanup(struct sprd_iommu_domain *dom) pgt_size =sprd_iommu_pgt_size (&dom->domain);dma_free_coherent (dom->sdev->dev, pgt_size, dom->pgt_va, dom->pgt_pa); - dom->sdev =NULL ;sprd_iommu_hw_en (dom->sdev, false); + dom->sdev =NULL ; }static void sprd_iommu_domain_free (struct iommu_domain *domain)
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 438/440 io_uring: fix io_match_task must_hold
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pavel Begunkov <[email protected]>
[ Upstream commit e142e9cd8891b0c6f277ac2c2c254199a6aa56e3 ]
The __must_hold annotation in io_match_task() uses a non existing parameter "req", fix it.
--- io_uring/timeout.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
io_uring/timeout.c +1 -1
@@ -601,7 +601,7 @@ void io_queue_linked_timeout(struct io_kiocb *req)static bool io_match_task (struct io_kiocb *head,struct task_struct *task,bool cancel_all) - __must_hold(&req->ctx->timeout_lock) + __must_hold(&head->ctx->timeout_lock) {struct io_kiocb *req;
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 439/440 nvme-pci: add missing condition check for existence of mapped data
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Leon Romanovsky <[email protected]>
[ Upstream commit c31fad1470389666ac7169fe43aa65bf5b7e2cfd ]
nvme_map_data() is called when request has physical segments, hence the nvme_unmap_data() should have same condition to avoid dereference.
--- drivers/nvme/host/pci.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/nvme/host/pci.c +2 -1
@@ -910,7 +910,8 @@ static blk_status_t nvme_prep_rq(struct nvme_dev *dev, struct request *req)blk_mq_start_request (req);return BLK_STS_OK ; out_unmap_data: -nvme_unmap_data (dev, req); +if (blk_rq_nr_phys_segments (req)) +nvme_unmap_data (dev, req); out_free_cmd:nvme_cleanup_cmd (req);return ret;
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 440/440 fs: dont allow non-init s_user_ns for filesystems without FS_USERNS_MOUNT
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Seth Forshee (DigitalOcean) <[email protected]>
[ Upstream commit e1c5ae59c0f22f7fe5c07fb5513a29e4aad868c9 ]
Christian noticed that it is possible for a privileged user to mount most filesystems with a non-initial user namespace in sb->s_user_ns. When fsopen() is called in a non-init namespace the caller's namespace is recorded in fs_context->user_ns. If the returned file descriptor is then passed to a process priviliged in init_user_ns, that process can call fsconfig(fd_fs, FSCONFIG_CMD_CREATE), creating a new superblock with sb->s_user_ns set to the namespace of the process which called fsopen().
This is problematic. We cannot assume that any filesystem which does not set FS_USERNS_MOUNT has been written with a non-initial s_user_ns in mind, increasing the risk for bugs and security issues.
Prevent this by returning EPERM from sget_fc() when FS_USERNS_MOUNT is not set for the filesystem and a non-initial user namespace will be used. sget() does not need to be updated as it always uses the user namespace of the current context, or the initial user namespace if SB_SUBMOUNT is set.
--- fs/super.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
fs/super.c +11 -0
@@ -569,6 +569,17 @@ struct super_block *sget_fc(struct fs_context *fc,struct user_namespace *user_ns = fc->global ? &init_user_ns : fc->user_ns;int err; +/* +* Never allow s_user_ns != &init_user_ns when FS_USERNS_MOUNT is +* not set, as the filesystem is likely unprepared to handle it. +* This can happen when fsconfig() is called from init_user_ns with +* an fs_fd opened in another user namespace. +*/ +if (user_ns != &init_user_ns && !(fc->fs_type->fs_flags &FS_USERNS_MOUNT )) { +errorfc (fc,"VFS: Mounting from non-initial user namespace is not allowed" ); +return ERR_PTR (-EPERM ); + } + retry:spin_lock (&sb_lock);if (test) {
Signature · 1 line
2.43.0
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.103 release. There are 440 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 Thu, 01 Aug 2024 15:14:54 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.103-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on BMIPS_GENERIC:
Signature · 1 line
Florian
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.103 release. There are 440 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 Thu, 01 Aug 2024 15:14:54 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.103-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and failed to boot on my test system. Panic during boot. I will work on finding the problem commit.
thanks,
-- Shuah
Hi,
could be the same issue as for me, see [1] for details.
[1]:
https://lore.kernel.org/stable/[email protected]/
Does applying 6259151c04d4e0085e00d2dcb471ebdd1778e72e from mainline (adapt hunk #2 to cleanly apply) help in your case, too, or do you maybe detected a different issue?
Cheers,
Frank
Quoted 11 lines · Frank Scheiner
Hi,
could be the same issue as for me, see [1] for details.
[1]:
https://lore.kernel.org/stable/[email protected]/Does applying
6259151c04d4e0085e00d2dcb471ebdd1778e72efrom mainline (adapt hunk #2 to cleanly apply) help in your case, too, or do you maybe detected a different issue?
Thank you for the tip. I will try this first to see if this fixes the problem for me.
thanks,
-- Shuah
Dear Greg,
6259151c04d4e0085e00d2dcb471ebdd1778e72e from mainline is missing in 6.1.103-rc1 and completes 39823b47bbd40502632ffba90ebb34fff7c8b5e8.
Please note that the second hunk from 6259151 needs to be modified to cleanly apply to 6.1.103-rc1. Example on [1].
****
## Long version ##
This patch series breaks operation of the hp-sim kernel in ski. I think it happens when trying to access the ext4 root FS in the simulation, see for example [2] for more details.
[2]: https://github.com/linux-ia64/linux-stable-rc/issues/3
From the call trace:
``` [...] [<a0000001000263f0>] die+0x1b0/0x3e0 [<a00000010004bd40>] ia64_do_page_fault+0x680/0x9c0 [<a00000010000c4e0>] ia64_leave_kernel+0x0/0x280 [<a00000010063f6a0>] dd_limit_depth+0x80/0x140 [...] ```
...I tracked it down to [3] and following the linked discussion ([4]), this is actually patch 2 of 2. And 1 of 2 ([5]) is in upstream, but not in 6.1.103-rc1.
[4]: https://lore.kernel.org/all/[email protected]/
Applying that patch ([5]) (plus adapting hunk #2 of it) on top of 6.1.103-rc1 fixes it for me ([6]).
[6]:
https://github.com/linux-ia64/linux-stable-rc/actions/runs/10170700172#summary-28130632329
Cheers,
Frank
Greg KH
maintainerQuoted 40 lines · Frank Scheiner
Dear Greg,
6259151c04d4e0085e00d2dcb471ebdd1778e72efrom mainline is missing in 6.1.103-rc1 and completes39823b47bbd40502632ffba90ebb34fff7c8b5e8.Please note that the second hunk from 6259151 needs to be modified to cleanly apply to 6.1.103-rc1. Example on [1].
****
## Long version ##
This patch series breaks operation of the hp-sim kernel in ski. I think it happens when trying to access the ext4 root FS in the simulation, see for example [2] for more details.
[2]: https://github.com/linux-ia64/linux-stable-rc/issues/3
From the call trace:
``` [...] [<a0000001000263f0>] die+0x1b0/0x3e0 [<a00000010004bd40>] ia64_do_page_fault+0x680/0x9c0 [<a00000010000c4e0>] ia64_leave_kernel+0x0/0x280 [<a00000010063f6a0>] dd_limit_depth+0x80/0x140 [...] ```...I tracked it down to [3] and following the linked discussion ([4]), this is actually patch 2 of 2. And 1 of 2 ([5]) is in upstream, but not in 6.1.103-rc1.
Quoted 8 lines
Applying that patch ([5]) (plus adapting hunk #2 of it) on top of 6.1.103-rc1 fixes it for me ([6]).
[6]:
https://github.com/linux-ia64/linux-stable-rc/actions/runs/10170700172#summary-28130632329
Thanks for this, I'll just drop the original offending commit here as that seems like the simplest way. If these really need to be in the 6.1.y tree, I'll be glad to take a backported series that people have tested to verify it all works properly.
greg k-h
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.103 release. There are 440 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 Thu, 01 Aug 2024 15:14:54 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.103-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
As others reported the boot failures and bisection results. I started validating 6.1.103-rc2 results.
[only for the record]
The stable-rc 6.1 boot failed on all devices due to the following kernel panic.
Boot crash log:
----------
<1>[ 6.427635] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0 <1>[ 6.428491] Mem abort info: <1>[ 6.428852] ESR = 0x0000000096000004 <1>[ 6.429458] EC = 0x25: DABT (current EL), IL = 32 bits <1>[ 6.430263] SET = 0, FnV = 0 <1>[ 6.430677] EA = 0, S1PTW = 0 <1>[ 6.431170] FSC = 0x04: level 0 translation fault <1>[ 6.431711] Data abort info: <1>[ 6.432167] ISV = 0, ISS = 0x00000004 <1>[ 6.432667] CM = 0, WnR = 0 <1>[ 6.433136] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000100005000 <1>[ 6.433848] [00000000000000d0] pgd=0000000000000000, p4d=0000000000000000 <0>[ 6.435845] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP <4>[ 6.436795] Modules linked in: ip_tables x_tables <4>[ 6.437973] CPU: 1 PID: 1 Comm: systemd Tainted: G N 6.1.103-rc1 #1 <4>[ 6.438884] Hardware name: linux,dummy-virt (DT) <4>[ 6.439800] pstate: 02400009 (nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--) <4>[ 6.440501] pc : dd_limit_depth (block/mq-deadline.c:609 block/mq-deadline.c:630) <4>[ 6.442475] lr : __blk_mq_alloc_requests (block/blk-mq.c:474) <4>[ 6.443041] sp : ffff80000802b7a0 <4>[ 6.443397] x29: ffff80000802b7b0 x28: 7fffffffffffffff x27: 0000000000000000 <4>[ 6.444406] x26: ffffa2ac0d3e5328 x25: ffff0000c0ad9cc0 x24: ffff0000c15986a0 <4>[ 6.445160] x23: 0000000000000001 x22: ffff0000c0ad9cc0 x21: ffff80000802ba38 <4>[ 6.445905] x20: ffff0000c0ad9cc0 x19: ffff80000802b820 x18: 0000000000000000 <4>[ 6.446654] x17: 0000000000000000 x16: 0000000000000000 x15: ffffffffffffffff <4>[ 6.447404] x14: ffffffffffffffff x13: ffffffffffffffff x12: ffffffffffffffff <4>[ 6.448159] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa2ac0c60feb0 <4>[ 6.448953] x8 : ffff80000802b668 x7 : 0000000000000000 x6 : 0000000000000001 <4>[ 6.449694] x5 : ffffa2ac0ea3f000 x4 : 0000000000000000 x3 : ffff0000c0f7bc00 <4>[ 6.450440] x2 : ffff0000c0ad9cc0 x1 : ffff80000802b820 x0 : 0000000000000000 <4>[ 6.451329] Call trace: <4>[ 6.451720] dd_limit_depth (block/mq-deadline.c:609 block/mq-deadline.c:630) <4>[ 6.452228] blk_mq_submit_bio (block/blk-mq.c:2911 block/blk-mq.c:3011) <4>[ 6.452712] __submit_bio (block/blk-core.c:595) <4>[ 6.453098] submit_bio_noacct_nocheck (include/linux/bio.h:614 block/blk-core.c:668 block/blk-core.c:696) <4>[ 6.453610] submit_bio_noacct (block/blk-core.c:799) <4>[ 6.454026] submit_bio (block/blk-core.c:828) <4>[ 6.454440] ext4_io_submit (fs/ext4/page-io.c:380) <4>[ 6.454884] ext4_writepages (fs/ext4/inode.c:2876) <4>[ 6.455328] do_writepages (mm/page-writeback.c:2491) <4>[ 6.455788] filemap_fdatawrite_wbc (mm/filemap.c:388 mm/filemap.c:378) <4>[ 6.456243] __filemap_fdatawrite_range (mm/filemap.c:422) <4>[ 6.456750] file_write_and_wait_range (mm/filemap.c:774) <4>[ 6.457249] ext4_sync_file (fs/ext4/fsync.c:151) <4>[ 6.457644] vfs_fsync_range (fs/sync.c:189) <4>[ 6.458095] do_fsync (fs/sync.c:202 fs/sync.c:212) <4>[ 6.458491] __arm64_sys_fsync (fs/sync.c:218) <4>[ 6.458899] invoke_syscall (arch/arm64/include/asm/current.h:19 arch/arm64/kernel/syscall.c:57) <4>[ 6.459349] el0_svc_common.constprop.0 (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/syscall.c:148) <4>[ 6.459864] do_el0_svc (arch/arm64/kernel/syscall.c:205) <4>[ 6.460272] el0_svc (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/entry-common.c:133 arch/arm64/kernel/entry-common.c:142 arch/arm64/kernel/entry-common.c:638) <4>[ 6.460644] el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:656) <4>[ 6.461099] el0t_64_sync (arch/arm64/kernel/entry.S:585) <0>[ 6.461765] Code: f9400022 d50323bf f9401820 f9400443 (f9406802)
All code
========
0: f9400022 ldr x2, [x1]
4: d50323bf autiasp
8: f9401820 ldr x0, [x1, #48]
c: f9400443 ldr x3, [x2, #8]
10:* f9406802 ldr x2, [x0, #208] <-- trapping instruction
Code starting with the faulting instruction
===========================================
0: f9406802 ldr x2, [x0, #208]
<4>[ 6.463039] ---[ end trace 0000000000000000 ]--- <4>[ 6.464924] ------------[ cut here ]------------ <4>[ 6.465459] WARNING: CPU: 1 PID: 1 at kernel/exit.c:816 do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.466537] Modules linked in: ip_tables x_tables <4>[ 6.467108] CPU: 1 PID: 1 Comm: systemd Tainted: G D N 6.1.103-rc1 #1 <4>[ 6.467792] Hardware name: linux,dummy-virt (DT) <4>[ 6.468226] pstate: 42400009 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--) <4>[ 6.468843] pc : do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.469218] lr : do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.469612] sp : ffff80000802b370 <4>[ 6.469941] x29: ffff80000802b3a0 x28: ffffa2ac0dbe3f48 x27: ffffa2ac0dbe3f40 <4>[ 6.470683] x26: 0000000000000000 x25: 0000000000000001 x24: ffff80000802b472 <4>[ 6.471437] x23: 0000000000000001 x22: 000000000000000b x21: ffff0000c02c0000 <4>[ 6.472185] x20: ffff0000c02dc000 x19: ffff0000c02b8000 x18: 0000000000000006 <4>[ 6.472916] x17: 3030303030303030 x16: 3030303030303020 x15: ffff80000802af00 <4>[ 6.473652] x14: 0000000000000000 x13: 205d393330333634 x12: 2e36202020205b3e <4>[ 6.474386] x11: 3030303030206563 x10: ffffa2ac0eabb978 x9 : ffffa2ac0d379d20 <4>[ 6.475118] x8 : ffff80000802b278 x7 : 0000000000000000 x6 : 0000000000000001 <4>[ 6.475845] x5 : ffffa2ac0ea3f000 x4 : ffffa2ac0ea3f2e8 x3 : 0000000000000000 <4>[ 6.476576] x2 : ffff0000c02b8000 x1 : ffff0000c02b8000 x0 : ffff80000802ba38 <4>[ 6.477310] Call trace: <4>[ 6.477595] do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.477948] make_task_dead
(arch/arm64/include/asm/atomic_ll_sc.h:95 (discriminator 2) arch/arm64/include/asm/atomic.h:52 (discriminator 2) include/linux/atomic/atomic-arch-fallback.h:440 (discriminator 2) include/linux/atomic/atomic-instrumented.h:199 (discriminator 2) kernel/exit.c:968 (discriminator 2))
<4>[ 6.478357] die (arch/arm64/kernel/traps.c:239) <4>[ 6.478697] die_kernel_fault (arch/arm64/mm/fault.c:307) <4>[ 6.479134] __do_kernel_fault (arch/arm64/mm/fault.c:404) <4>[ 6.479574] do_page_fault (arch/arm64/mm/fault.c:658) <4>[ 6.479962] do_translation_fault (arch/arm64/mm/fault.c:671) <4>[ 6.480411] do_mem_abort (arch/arm64/mm/fault.c:803 (discriminator 1)) <4>[ 6.480781] el1_abort (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/entry-common.c:368) <4>[ 6.481142] el1h_64_sync_handler (arch/arm64/kernel/entry-common.c:455) <4>[ 6.481588] el1h_64_sync (arch/arm64/kernel/entry.S:580) <4>[ 6.481958] dd_limit_depth (block/mq-deadline.c:609 block/mq-deadline.c:630) <4>[ 6.482355] blk_mq_submit_bio (block/blk-mq.c:2911 block/blk-mq.c:3011) <4>[ 6.482778] __submit_bio (block/blk-core.c:595) <4>[ 6.483184] submit_bio_noacct_nocheck (include/linux/bio.h:614 block/blk-core.c:668 block/blk-core.c:696) <4>[ 6.483650] submit_bio_noacct (block/blk-core.c:799) <4>[ 6.484098] submit_bio (block/blk-core.c:828) <4>[ 6.484454] ext4_io_submit (fs/ext4/page-io.c:380) <4>[ 6.484858] ext4_writepages (fs/ext4/inode.c:2876) <4>[ 6.485285] do_writepages (mm/page-writeback.c:2491) <4>[ 6.485670] filemap_fdatawrite_wbc (mm/filemap.c:388 mm/filemap.c:378) <4>[ 6.486122] __filemap_fdatawrite_range (mm/filemap.c:422) <4>[ 6.486587] file_write_and_wait_range (mm/filemap.c:774) <4>[ 6.487048] ext4_sync_file (fs/ext4/fsync.c:151) <4>[ 6.487463] vfs_fsync_range (fs/sync.c:189) <4>[ 6.487848] do_fsync (fs/sync.c:202 fs/sync.c:212) <4>[ 6.488223] __arm64_sys_fsync (fs/sync.c:218) <4>[ 6.488649] invoke_syscall (arch/arm64/include/asm/current.h:19 arch/arm64/kernel/syscall.c:57) <4>[ 6.489039] el0_svc_common.constprop.0 (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/syscall.c:148) <4>[ 6.489522] do_el0_svc (arch/arm64/kernel/syscall.c:205) <4>[ 6.489876] el0_svc (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/entry-common.c:133 arch/arm64/kernel/entry-common.c:142 arch/arm64/kernel/entry-common.c:638) <4>[ 6.490212] el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:656) <4>[ 6.490682] el0t_64_sync (arch/arm64/kernel/entry.S:585) <4>[ 6.491191] ---[ end trace 0000000000000000 ]--- <0>[ 6.492871] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b <2>[ 6.493803] SMP: stopping secondary CPUs <0>[ 6.494951] Kernel Offset: 0x22ac04000000 from 0xffff800008000000 <0>[ 6.495536] PHYS_OFFSET: 0x40000000 <0>[ 6.495944] CPU features: 0x00000,000d3cbf,e69a773f <0>[ 6.496943] Memory Limit: none <0>[ 6.497664] ---[ end Kernel panic - not syncing: Attempted to
kill init! exitcode=0x0000000b ]---
Links to boot log:
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186/testrun/24742768/suite/boot/test/gcc-13-lkftconfig-devicetree/log
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186/testrun/24742768/suite/boot/test/gcc-13-lkftconfig-devicetree/details/
- Config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2jyP6yz35Go9caJsvrdNOlq0X9t/config
- Build: https://storage.tuxsuite.com/public/linaro/lkft/builds/2jyP6yz35Go9caJsvrdNOlq0X9t/
metadata:
----------
## Build
* kernel: 6.1.103-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit: a90fe3a941868870c281a880358b14d42f530b07
* git describe: v6.1.102-441-ga90fe3a94186
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186
--
Linaro LKFT
https://lkft.linaro.org
Jens Axboe
maintainerQuoted 215 lines · Naresh Kamboju
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.103 release. There are 440 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 Thu, 01 Aug 2024 15:14:54 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.103-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
As others reported the boot failures and bisection results. I started validating 6.1.103-rc2 results.
[only for the record]
The stable-rc 6.1 boot failed on all devices due to the following kernel panic.Boot crash log:
----------<1>[ 6.427635] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0 <1>[ 6.428491] Mem abort info: <1>[ 6.428852] ESR = 0x0000000096000004 <1>[ 6.429458] EC = 0x25: DABT (current EL), IL = 32 bits <1>[ 6.430263] SET = 0, FnV = 0 <1>[ 6.430677] EA = 0, S1PTW = 0 <1>[ 6.431170] FSC = 0x04: level 0 translation fault <1>[ 6.431711] Data abort info: <1>[ 6.432167] ISV = 0, ISS = 0x00000004 <1>[ 6.432667] CM = 0, WnR = 0 <1>[ 6.433136] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000100005000 <1>[ 6.433848] [00000000000000d0] pgd=0000000000000000, p4d=0000000000000000 <0>[ 6.435845] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP <4>[ 6.436795] Modules linked in: ip_tables x_tables <4>[ 6.437973] CPU: 1 PID: 1 Comm: systemd Tainted: G N 6.1.103-rc1 #1 <4>[ 6.438884] Hardware name: linux,dummy-virt (DT) <4>[ 6.439800] pstate: 02400009 (nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--) <4>[ 6.440501] pc : dd_limit_depth (block/mq-deadline.c:609 block/mq-deadline.c:630) <4>[ 6.442475] lr : __blk_mq_alloc_requests (block/blk-mq.c:474) <4>[ 6.443041] sp : ffff80000802b7a0 <4>[ 6.443397] x29: ffff80000802b7b0 x28: 7fffffffffffffff x27: 0000000000000000 <4>[ 6.444406] x26: ffffa2ac0d3e5328 x25: ffff0000c0ad9cc0 x24: ffff0000c15986a0 <4>[ 6.445160] x23: 0000000000000001 x22: ffff0000c0ad9cc0 x21: ffff80000802ba38 <4>[ 6.445905] x20: ffff0000c0ad9cc0 x19: ffff80000802b820 x18: 0000000000000000 <4>[ 6.446654] x17: 0000000000000000 x16: 0000000000000000 x15: ffffffffffffffff <4>[ 6.447404] x14: ffffffffffffffff x13: ffffffffffffffff x12: ffffffffffffffff <4>[ 6.448159] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa2ac0c60feb0 <4>[ 6.448953] x8 : ffff80000802b668 x7 : 0000000000000000 x6 : 0000000000000001 <4>[ 6.449694] x5 : ffffa2ac0ea3f000 x4 : 0000000000000000 x3 : ffff0000c0f7bc00 <4>[ 6.450440] x2 : ffff0000c0ad9cc0 x1 : ffff80000802b820 x0 : 0000000000000000 <4>[ 6.451329] Call trace: <4>[ 6.451720] dd_limit_depth (block/mq-deadline.c:609 block/mq-deadline.c:630) <4>[ 6.452228] blk_mq_submit_bio (block/blk-mq.c:2911 block/blk-mq.c:3011) <4>[ 6.452712] __submit_bio (block/blk-core.c:595) <4>[ 6.453098] submit_bio_noacct_nocheck (include/linux/bio.h:614 block/blk-core.c:668 block/blk-core.c:696) <4>[ 6.453610] submit_bio_noacct (block/blk-core.c:799) <4>[ 6.454026] submit_bio (block/blk-core.c:828) <4>[ 6.454440] ext4_io_submit (fs/ext4/page-io.c:380) <4>[ 6.454884] ext4_writepages (fs/ext4/inode.c:2876) <4>[ 6.455328] do_writepages (mm/page-writeback.c:2491) <4>[ 6.455788] filemap_fdatawrite_wbc (mm/filemap.c:388 mm/filemap.c:378) <4>[ 6.456243] __filemap_fdatawrite_range (mm/filemap.c:422) <4>[ 6.456750] file_write_and_wait_range (mm/filemap.c:774) <4>[ 6.457249] ext4_sync_file (fs/ext4/fsync.c:151) <4>[ 6.457644] vfs_fsync_range (fs/sync.c:189) <4>[ 6.458095] do_fsync (fs/sync.c:202 fs/sync.c:212) <4>[ 6.458491] __arm64_sys_fsync (fs/sync.c:218) <4>[ 6.458899] invoke_syscall (arch/arm64/include/asm/current.h:19 arch/arm64/kernel/syscall.c:57) <4>[ 6.459349] el0_svc_common.constprop.0 (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/syscall.c:148) <4>[ 6.459864] do_el0_svc (arch/arm64/kernel/syscall.c:205) <4>[ 6.460272] el0_svc (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/entry-common.c:133 arch/arm64/kernel/entry-common.c:142 arch/arm64/kernel/entry-common.c:638) <4>[ 6.460644] el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:656) <4>[ 6.461099] el0t_64_sync (arch/arm64/kernel/entry.S:585) <0>[ 6.461765] Code: f9400022 d50323bf f9401820 f9400443 (f9406802)All code
========
0:f9400022ldr x2, [x1]
4:d50323bfautiasp
8:f9401820ldr x0, [x1, #48]
c:f9400443ldr x3, [x2, #8]
10:*f9406802ldr x2, [x0, #208] <-- trapping instructionCode starting with the faulting instruction
===========================================
0:f9406802ldr x2, [x0, #208]<4>[ 6.463039] ---[ end trace 0000000000000000 ]--- <4>[ 6.464924] ------------[ cut here ]------------ <4>[ 6.465459] WARNING: CPU: 1 PID: 1 at kernel/exit.c:816 do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.466537] Modules linked in: ip_tables x_tables <4>[ 6.467108] CPU: 1 PID: 1 Comm: systemd Tainted: G D N 6.1.103-rc1 #1 <4>[ 6.467792] Hardware name: linux,dummy-virt (DT) <4>[ 6.468226] pstate: 42400009 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--) <4>[ 6.468843] pc : do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.469218] lr : do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.469612] sp : ffff80000802b370 <4>[ 6.469941] x29: ffff80000802b3a0 x28: ffffa2ac0dbe3f48 x27: ffffa2ac0dbe3f40 <4>[ 6.470683] x26: 0000000000000000 x25: 0000000000000001 x24: ffff80000802b472 <4>[ 6.471437] x23: 0000000000000001 x22: 000000000000000b x21: ffff0000c02c0000 <4>[ 6.472185] x20: ffff0000c02dc000 x19: ffff0000c02b8000 x18: 0000000000000006 <4>[ 6.472916] x17: 3030303030303030 x16: 3030303030303020 x15: ffff80000802af00 <4>[ 6.473652] x14: 0000000000000000 x13: 205d393330333634 x12: 2e36202020205b3e <4>[ 6.474386] x11: 3030303030206563 x10: ffffa2ac0eabb978 x9 : ffffa2ac0d379d20 <4>[ 6.475118] x8 : ffff80000802b278 x7 : 0000000000000000 x6 : 0000000000000001 <4>[ 6.475845] x5 : ffffa2ac0ea3f000 x4 : ffffa2ac0ea3f2e8 x3 : 0000000000000000 <4>[ 6.476576] x2 : ffff0000c02b8000 x1 : ffff0000c02b8000 x0 : ffff80000802ba38 <4>[ 6.477310] Call trace: <4>[ 6.477595] do_exit (kernel/exit.c:816 (discriminator 1)) <4>[ 6.477948] make_task_dead(
arch/arm64/include/asm/atomic_ll_sc.h:95(discriminator 2)arch/arm64/include/asm/atomic.h:52(discriminator 2)include/linux/atomic/atomic-arch-fallback.h:440(discriminator 2)include/linux/atomic/atomic-instrumented.h:199(discriminator 2)kernel/exit.c:968(discriminator 2))<4>[ 6.478357] die (arch/arm64/kernel/traps.c:239) <4>[ 6.478697] die_kernel_fault (arch/arm64/mm/fault.c:307) <4>[ 6.479134] __do_kernel_fault (arch/arm64/mm/fault.c:404) <4>[ 6.479574] do_page_fault (arch/arm64/mm/fault.c:658) <4>[ 6.479962] do_translation_fault (arch/arm64/mm/fault.c:671) <4>[ 6.480411] do_mem_abort (arch/arm64/mm/fault.c:803 (discriminator 1)) <4>[ 6.480781] el1_abort (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/entry-common.c:368) <4>[ 6.481142] el1h_64_sync_handler (arch/arm64/kernel/entry-common.c:455) <4>[ 6.481588] el1h_64_sync (arch/arm64/kernel/entry.S:580) <4>[ 6.481958] dd_limit_depth (block/mq-deadline.c:609 block/mq-deadline.c:630) <4>[ 6.482355] blk_mq_submit_bio (block/blk-mq.c:2911 block/blk-mq.c:3011) <4>[ 6.482778] __submit_bio (block/blk-core.c:595) <4>[ 6.483184] submit_bio_noacct_nocheck (include/linux/bio.h:614 block/blk-core.c:668 block/blk-core.c:696) <4>[ 6.483650] submit_bio_noacct (block/blk-core.c:799) <4>[ 6.484098] submit_bio (block/blk-core.c:828) <4>[ 6.484454] ext4_io_submit (fs/ext4/page-io.c:380) <4>[ 6.484858] ext4_writepages (fs/ext4/inode.c:2876) <4>[ 6.485285] do_writepages (mm/page-writeback.c:2491) <4>[ 6.485670] filemap_fdatawrite_wbc (mm/filemap.c:388 mm/filemap.c:378) <4>[ 6.486122] __filemap_fdatawrite_range (mm/filemap.c:422) <4>[ 6.486587] file_write_and_wait_range (mm/filemap.c:774) <4>[ 6.487048] ext4_sync_file (fs/ext4/fsync.c:151) <4>[ 6.487463] vfs_fsync_range (fs/sync.c:189) <4>[ 6.487848] do_fsync (fs/sync.c:202 fs/sync.c:212) <4>[ 6.488223] __arm64_sys_fsync (fs/sync.c:218) <4>[ 6.488649] invoke_syscall (arch/arm64/include/asm/current.h:19 arch/arm64/kernel/syscall.c:57) <4>[ 6.489039] el0_svc_common.constprop.0 (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/syscall.c:148) <4>[ 6.489522] do_el0_svc (arch/arm64/kernel/syscall.c:205) <4>[ 6.489876] el0_svc (arch/arm64/include/asm/daifflags.h:28 arch/arm64/kernel/entry-common.c:133 arch/arm64/kernel/entry-common.c:142 arch/arm64/kernel/entry-common.c:638) <4>[ 6.490212] el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:656) <4>[ 6.490682] el0t_64_sync (arch/arm64/kernel/entry.S:585) <4>[ 6.491191] ---[ end trace 0000000000000000 ]--- <0>[ 6.492871] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b <2>[ 6.493803] SMP: stopping secondary CPUs <0>[ 6.494951] Kernel Offset: 0x22ac04000000 from 0xffff800008000000 <0>[ 6.495536] PHYS_OFFSET: 0x40000000 <0>[ 6.495944] CPU features: 0x00000,000d3cbf,e69a773f <0>[ 6.496943] Memory Limit: none <0>[ 6.497664] ---[ end Kernel panic - not syncing: Attempted tokill init! exitcode=0x0000000b ]---
Links to boot log:
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186/testrun/24742768/suite/boot/test/gcc-13-lkftconfig-devicetree/log
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186/testrun/24742768/suite/boot/test/gcc-13-lkftconfig-devicetree/details/
- Config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2jyP6yz35Go9caJsvrdNOlq0X9t/config
- Build: https://storage.tuxsuite.com/public/linaro/lkft/builds/2jyP6yz35Go9caJsvrdNOlq0X9t/
Quoted 9 lines
metadata:
----------
## Build
* kernel: 6.1.103-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit:a90fe3a941868870c281a880358b14d42f530b07
* git describe: v6.1.102-441-ga90fe3a94186
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186
I built and booted 6.1.103-rc3 and didn't hit anything. Does it still trigger with that one? If yes, how do I reproduce this?
There are no deadline changes since 6.1.102, and the block side is just some integrity bits, which don't look suspicious. The other part this could potentially be is the sbitmap changes, but...
Signature · 1 line
Jens Axboe
Quoted 9 lines · Jens Axboe
Quoted 8 lines
----------
## Build
* kernel: 6.1.103-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit:a90fe3a941868870c281a880358b14d42f530b07
* git describe: v6.1.102-441-ga90fe3a94186
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186
Quoted 7 lines
I built and booted 6.1.103-rc3 and didn't hit anything. Does it still trigger with that one? If yes, how do I reproduce this?
There are no deadline changes since 6.1.102, and the block side is just some integrity bits, which don't look suspicious. The other part this could potentially be is the sbitmap changes, but...
I believe these were fixed in -rc2. We're on -rc3 now.
regards,
dan carpenter
Jens Axboe
maintainerQuoted 13 lines · Dan Carpenter
Quoted 12 lines · Jens Axboe
Quoted 8 lines
----------
## Build
* kernel: 6.1.103-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit:a90fe3a941868870c281a880358b14d42f530b07
* git describe: v6.1.102-441-ga90fe3a94186
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.102-441-ga90fe3a94186I built and booted 6.1.103-rc3 and didn't hit anything. Does it still trigger with that one? If yes, how do I reproduce this?
Quoted 6 lines
Quoted 4 lines
There are no deadline changes since 6.1.102, and the block side is just some integrity bits, which don't look suspicious. The other part this could potentially be is the sbitmap changes, but...
I believe these were fixed in -rc2. We're on -rc3 now.
OK good, thanks.
Signature · 1 line
Jens Axboe
Am 30.07.2024 um 17:43 schrieb Greg Kroah-Hartman:
Quoted 7 lines
This is the start of the stable review cycle for the 6.1.103 release. There are 440 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 Thu, 01 Aug 2024 15:14:54 +0000. Anything received after that time might be too late.
Just for the record: this builds on my 2-socket Ivy Bridge Xeon E5-2697 v2 server, but fails to boot due to a kernel panic which others have already reported.
Looking for testing -rc2...
Beste Grüße,
Peter Schneider
Signature · 8 lines
Climb the mountain not to plant your flag, but to embrace the challenge, enjoy the air and behold the view. Climb it so you can see the world, not so the world can see you. -- David McCullough Jr. OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244 Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc https://keys.mailvelope.com/pks/lookup?op=get&[email protected] https://keys.mailvelope.com/pks/lookup?op=get&[email protected]
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.103 release. There are 440 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.
Quoted 9 lines
Responses should be made by Thu, 01 Aug 2024 15:14:54 +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.1.103-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.
KernelCI report for stable-rc/linux-6.1.y for this week :-
Date: 2024-07-30
## Build failures:
No **new** build failures seen for the stable-rc/linux-6.1.y commit head \o/
## Boot failures:
No **new** boot failures seen for the stable-rc/linux-6.1.y commit head \o/
Thanks,
Shreeya Patel