From 45517cb74517fc0b255d140bc5bb14c578f5f123 Mon Sep 17 00:00:00 2001 From: Greg Kroah-Hartman Date: Mon, 4 Jul 2022 09:50:10 +0200 Subject: [PATCH] 5.15-stable patches added patches: dm-raid-fix-accesses-beyond-end-of-raid-member-array.patch dm-raid-fix-kasan-warning-in-raid5_add_disks.patch drm-amdgpu-to-flush-tlb-for-mmhub-of-raven-series.patch ipv6-take-care-of-disable_policy-when-restoring-routes.patch ksmbd-check-invalid-fileoffset-and-beyondfinalzero-in-fsctl_zero_data.patch ksmbd-set-the-range-of-bytes-to-zero-without-extending-file-size-in-fsctl_zero_data.patch ksmbd-use-vfs_llseek-instead-of-dereferencing-null.patch net-phy-don-t-trigger-state-machine-while-in-suspend.patch nvdimm-fix-badblocks-clear-off-by-one-error.patch nvme-pci-add-nvme_quirk_bogus_nid-for-adata-im2p33f8abr1.patch nvme-pci-add-nvme_quirk_bogus_nid-for-adata-xpg-sx6000lnp-aka-spectrix-s40g.patch powerpc-book3e-fix-pud-allocation-size-in-map_kernel_page.patch powerpc-bpf-fix-use-of-user_pt_regs-in-uapi.patch powerpc-prom_init-fix-kernel-config-grep.patch revert-drm-amdgpu-display-set-vblank_disable_immediate-for-dc.patch --- ...sses-beyond-end-of-raid-member-array.patch | 118 +++++++++++++ ...fix-kasan-warning-in-raid5_add_disks.patch | 32 ++++ ...-flush-tlb-for-mmhub-of-raven-series.patch | 48 ++++++ ...disable_policy-when-restoring-routes.patch | 63 +++++++ ...d-beyondfinalzero-in-fsctl_zero_data.patch | 69 ++++++++ ...tending-file-size-in-fsctl_zero_data.patch | 37 ++++ ...llseek-instead-of-dereferencing-null.patch | 48 ++++++ ...igger-state-machine-while-in-suspend.patch | 161 ++++++++++++++++++ ...fix-badblocks-clear-off-by-one-error.patch | 38 +++++ ...irk_bogus_nid-for-adata-im2p33f8abr1.patch | 38 +++++ ...data-xpg-sx6000lnp-aka-spectrix-s40g.patch | 59 +++++++ ...d-allocation-size-in-map_kernel_page.patch | 48 ++++++ ...-bpf-fix-use-of-user_pt_regs-in-uapi.patch | 81 +++++++++ ...rpc-prom_init-fix-kernel-config-grep.patch | 33 ++++ ...-set-vblank_disable_immediate-for-dc.patch | 48 ++++++ queue-5.15/series | 15 ++ 16 files changed, 936 insertions(+) create mode 100644 queue-5.15/dm-raid-fix-accesses-beyond-end-of-raid-member-array.patch create mode 100644 queue-5.15/dm-raid-fix-kasan-warning-in-raid5_add_disks.patch create mode 100644 queue-5.15/drm-amdgpu-to-flush-tlb-for-mmhub-of-raven-series.patch create mode 100644 queue-5.15/ipv6-take-care-of-disable_policy-when-restoring-routes.patch create mode 100644 queue-5.15/ksmbd-check-invalid-fileoffset-and-beyondfinalzero-in-fsctl_zero_data.patch create mode 100644 queue-5.15/ksmbd-set-the-range-of-bytes-to-zero-without-extending-file-size-in-fsctl_zero_data.patch create mode 100644 queue-5.15/ksmbd-use-vfs_llseek-instead-of-dereferencing-null.patch create mode 100644 queue-5.15/net-phy-don-t-trigger-state-machine-while-in-suspend.patch create mode 100644 queue-5.15/nvdimm-fix-badblocks-clear-off-by-one-error.patch create mode 100644 queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-im2p33f8abr1.patch create mode 100644 queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-xpg-sx6000lnp-aka-spectrix-s40g.patch create mode 100644 queue-5.15/powerpc-book3e-fix-pud-allocation-size-in-map_kernel_page.patch create mode 100644 queue-5.15/powerpc-bpf-fix-use-of-user_pt_regs-in-uapi.patch create mode 100644 queue-5.15/powerpc-prom_init-fix-kernel-config-grep.patch create mode 100644 queue-5.15/revert-drm-amdgpu-display-set-vblank_disable_immediate-for-dc.patch create mode 100644 queue-5.15/series diff --git a/queue-5.15/dm-raid-fix-accesses-beyond-end-of-raid-member-array.patch b/queue-5.15/dm-raid-fix-accesses-beyond-end-of-raid-member-array.patch new file mode 100644 index 00000000000..44767afec75 --- /dev/null +++ b/queue-5.15/dm-raid-fix-accesses-beyond-end-of-raid-member-array.patch @@ -0,0 +1,118 @@ +From 332bd0778775d0cf105c4b9e03e460b590749916 Mon Sep 17 00:00:00 2001 +From: Heinz Mauelshagen +Date: Tue, 28 Jun 2022 00:37:22 +0200 +Subject: dm raid: fix accesses beyond end of raid member array + +From: Heinz Mauelshagen + +commit 332bd0778775d0cf105c4b9e03e460b590749916 upstream. + +On dm-raid table load (using raid_ctr), dm-raid allocates an array +rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks +is defined by the number of raid metadata and image tupples passed +into the target's constructor. + +In the case of RAID layout changes being requested, that number can be +different from the current number of members for existing raid sets as +defined in their superblocks. Example RAID layout changes include: +- raid1 legs being added/removed +- raid4/5/6/10 number of stripes changed (stripe reshaping) +- takeover to higher raid level (e.g. raid5 -> raid6) + +When accessing array members, rs->raid_disks must be used in control +loops instead of the potentially larger value in rs->md.raid_disks. +Otherwise it will cause memory access beyond the end of the rs->devs +array. + +Fix this by changing code that is prone to out-of-bounds access. +Also fix validate_raid_redundancy() to validate all devices that are +added. Also, use braces to help clean up raid_iterate_devices(). + +The out-of-bounds memory accesses was discovered using KASAN. + +This commit was verified to pass all LVM2 RAID tests (with KASAN +enabled). + +Cc: stable@vger.kernel.org +Signed-off-by: Heinz Mauelshagen +Signed-off-by: Mike Snitzer +Signed-off-by: Greg Kroah-Hartman +--- + drivers/md/dm-raid.c | 34 ++++++++++++++++++---------------- + 1 file changed, 18 insertions(+), 16 deletions(-) + +--- a/drivers/md/dm-raid.c ++++ b/drivers/md/dm-raid.c +@@ -1001,12 +1001,13 @@ static int validate_region_size(struct r + static int validate_raid_redundancy(struct raid_set *rs) + { + unsigned int i, rebuild_cnt = 0; +- unsigned int rebuilds_per_group = 0, copies; ++ unsigned int rebuilds_per_group = 0, copies, raid_disks; + unsigned int group_size, last_group_start; + +- for (i = 0; i < rs->md.raid_disks; i++) +- if (!test_bit(In_sync, &rs->dev[i].rdev.flags) || +- !rs->dev[i].rdev.sb_page) ++ for (i = 0; i < rs->raid_disks; i++) ++ if (!test_bit(FirstUse, &rs->dev[i].rdev.flags) && ++ ((!test_bit(In_sync, &rs->dev[i].rdev.flags) || ++ !rs->dev[i].rdev.sb_page))) + rebuild_cnt++; + + switch (rs->md.level) { +@@ -1046,8 +1047,9 @@ static int validate_raid_redundancy(stru + * A A B B C + * C D D E E + */ ++ raid_disks = min(rs->raid_disks, rs->md.raid_disks); + if (__is_raid10_near(rs->md.new_layout)) { +- for (i = 0; i < rs->md.raid_disks; i++) { ++ for (i = 0; i < raid_disks; i++) { + if (!(i % copies)) + rebuilds_per_group = 0; + if ((!rs->dev[i].rdev.sb_page || +@@ -1070,10 +1072,10 @@ static int validate_raid_redundancy(stru + * results in the need to treat the last (potentially larger) + * set differently. + */ +- group_size = (rs->md.raid_disks / copies); +- last_group_start = (rs->md.raid_disks / group_size) - 1; ++ group_size = (raid_disks / copies); ++ last_group_start = (raid_disks / group_size) - 1; + last_group_start *= group_size; +- for (i = 0; i < rs->md.raid_disks; i++) { ++ for (i = 0; i < raid_disks; i++) { + if (!(i % copies) && !(i > last_group_start)) + rebuilds_per_group = 0; + if ((!rs->dev[i].rdev.sb_page || +@@ -1588,7 +1590,7 @@ static sector_t __rdev_sectors(struct ra + { + int i; + +- for (i = 0; i < rs->md.raid_disks; i++) { ++ for (i = 0; i < rs->raid_disks; i++) { + struct md_rdev *rdev = &rs->dev[i].rdev; + + if (!test_bit(Journal, &rdev->flags) && +@@ -3771,13 +3773,13 @@ static int raid_iterate_devices(struct d + unsigned int i; + int r = 0; + +- for (i = 0; !r && i < rs->md.raid_disks; i++) +- if (rs->dev[i].data_dev) +- r = fn(ti, +- rs->dev[i].data_dev, +- 0, /* No offset on data devs */ +- rs->md.dev_sectors, +- data); ++ for (i = 0; !r && i < rs->raid_disks; i++) { ++ if (rs->dev[i].data_dev) { ++ r = fn(ti, rs->dev[i].data_dev, ++ 0, /* No offset on data devs */ ++ rs->md.dev_sectors, data); ++ } ++ } + + return r; + } diff --git a/queue-5.15/dm-raid-fix-kasan-warning-in-raid5_add_disks.patch b/queue-5.15/dm-raid-fix-kasan-warning-in-raid5_add_disks.patch new file mode 100644 index 00000000000..8007565d07f --- /dev/null +++ b/queue-5.15/dm-raid-fix-kasan-warning-in-raid5_add_disks.patch @@ -0,0 +1,32 @@ +From 617b365872a247480e9dcd50a32c8d1806b21861 Mon Sep 17 00:00:00 2001 +From: Mikulas Patocka +Date: Wed, 29 Jun 2022 13:40:57 -0400 +Subject: dm raid: fix KASAN warning in raid5_add_disks + +From: Mikulas Patocka + +commit 617b365872a247480e9dcd50a32c8d1806b21861 upstream. + +There's a KASAN warning in raid5_add_disk when running the LVM testsuite. +The warning happens in the test +lvconvert-raid-reshape-linear_to_raid6-single-type.sh. We fix the warning +by verifying that rdev->saved_raid_disk is within limits. + +Cc: stable@vger.kernel.org +Signed-off-by: Mikulas Patocka +Signed-off-by: Mike Snitzer +Signed-off-by: Greg Kroah-Hartman +--- + drivers/md/raid5.c | 1 + + 1 file changed, 1 insertion(+) + +--- a/drivers/md/raid5.c ++++ b/drivers/md/raid5.c +@@ -8026,6 +8026,7 @@ static int raid5_add_disk(struct mddev * + */ + if (rdev->saved_raid_disk >= 0 && + rdev->saved_raid_disk >= first && ++ rdev->saved_raid_disk <= last && + conf->disks[rdev->saved_raid_disk].rdev == NULL) + first = rdev->saved_raid_disk; + diff --git a/queue-5.15/drm-amdgpu-to-flush-tlb-for-mmhub-of-raven-series.patch b/queue-5.15/drm-amdgpu-to-flush-tlb-for-mmhub-of-raven-series.patch new file mode 100644 index 00000000000..7609e73e9c8 --- /dev/null +++ b/queue-5.15/drm-amdgpu-to-flush-tlb-for-mmhub-of-raven-series.patch @@ -0,0 +1,48 @@ +From 5cb0e3fb2c54eabfb3f932a1574bff1774946bc0 Mon Sep 17 00:00:00 2001 +From: Ruili Ji +Date: Wed, 22 Jun 2022 14:20:22 +0800 +Subject: drm/amdgpu: To flush tlb for MMHUB of RAVEN series + +From: Ruili Ji + +commit 5cb0e3fb2c54eabfb3f932a1574bff1774946bc0 upstream. + +amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:8 pasid:32769, for process test_basic pid 3305 thread test_basic pid 3305) +amdgpu: in page starting at address 0x00007ff990003000 from IH client 0x12 (VMC) +amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00840051 +amdgpu: Faulty UTCL2 client ID: MP1 (0x0) +amdgpu: MORE_FAULTS: 0x1 +amdgpu: WALKER_ERROR: 0x0 +amdgpu: PERMISSION_FAULTS: 0x5 +amdgpu: MAPPING_ERROR: 0x0 +amdgpu: RW: 0x1 + +When memory is allocated by kfd, no one triggers the tlb flush for MMHUB0. +There is page fault from MMHUB0. + +v2:fix indentation +v3:change subject and fix indentation + +Signed-off-by: Ruili Ji +Reviewed-by: Philip Yang +Reviewed-by: Aaron Liu +Acked-by: Alex Deucher +Signed-off-by: Alex Deucher +Cc: stable@vger.kernel.org +Signed-off-by: Greg Kroah-Hartman +--- + drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c ++++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c +@@ -768,7 +768,8 @@ int amdgpu_amdkfd_flush_gpu_tlb_pasid(st + struct amdgpu_device *adev = (struct amdgpu_device *)kgd; + bool all_hub = false; + +- if (adev->family == AMDGPU_FAMILY_AI) ++ if (adev->family == AMDGPU_FAMILY_AI || ++ adev->family == AMDGPU_FAMILY_RV) + all_hub = true; + + return amdgpu_gmc_flush_gpu_tlb_pasid(adev, pasid, flush_type, all_hub); diff --git a/queue-5.15/ipv6-take-care-of-disable_policy-when-restoring-routes.patch b/queue-5.15/ipv6-take-care-of-disable_policy-when-restoring-routes.patch new file mode 100644 index 00000000000..d9e448d42d3 --- /dev/null +++ b/queue-5.15/ipv6-take-care-of-disable_policy-when-restoring-routes.patch @@ -0,0 +1,63 @@ +From 3b0dc529f56b5f2328244130683210be98f16f7f Mon Sep 17 00:00:00 2001 +From: Nicolas Dichtel +Date: Thu, 23 Jun 2022 14:00:15 +0200 +Subject: ipv6: take care of disable_policy when restoring routes + +From: Nicolas Dichtel + +commit 3b0dc529f56b5f2328244130683210be98f16f7f upstream. + +When routes corresponding to addresses are restored by +fixup_permanent_addr(), the dst_nopolicy parameter was not set. +The typical use case is a user that configures an address on a down +interface and then put this interface up. + +Let's take care of this flag in addrconf_f6i_alloc(), so that every callers +benefit ont it. + +CC: stable@kernel.org +CC: David Forster +Fixes: df789fe75206 ("ipv6: Provide ipv6 version of "disable_policy" sysctl") +Reported-by: Siwar Zitouni +Signed-off-by: Nicolas Dichtel +Reviewed-by: David Ahern +Link: https://lore.kernel.org/r/20220623120015.32640-1-nicolas.dichtel@6wind.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + net/ipv6/addrconf.c | 4 ---- + net/ipv6/route.c | 9 ++++++++- + 2 files changed, 8 insertions(+), 5 deletions(-) + +--- a/net/ipv6/addrconf.c ++++ b/net/ipv6/addrconf.c +@@ -1111,10 +1111,6 @@ ipv6_add_addr(struct inet6_dev *idev, st + goto out; + } + +- if (net->ipv6.devconf_all->disable_policy || +- idev->cnf.disable_policy) +- f6i->dst_nopolicy = true; +- + neigh_parms_data_state_setall(idev->nd_parms); + + ifa->addr = *cfg->pfx; +--- a/net/ipv6/route.c ++++ b/net/ipv6/route.c +@@ -4590,8 +4590,15 @@ struct fib6_info *addrconf_f6i_alloc(str + } + + f6i = ip6_route_info_create(&cfg, gfp_flags, NULL); +- if (!IS_ERR(f6i)) ++ if (!IS_ERR(f6i)) { + f6i->dst_nocount = true; ++ ++ if (!anycast && ++ (net->ipv6.devconf_all->disable_policy || ++ idev->cnf.disable_policy)) ++ f6i->dst_nopolicy = true; ++ } ++ + return f6i; + } + diff --git a/queue-5.15/ksmbd-check-invalid-fileoffset-and-beyondfinalzero-in-fsctl_zero_data.patch b/queue-5.15/ksmbd-check-invalid-fileoffset-and-beyondfinalzero-in-fsctl_zero_data.patch new file mode 100644 index 00000000000..054196fc72f --- /dev/null +++ b/queue-5.15/ksmbd-check-invalid-fileoffset-and-beyondfinalzero-in-fsctl_zero_data.patch @@ -0,0 +1,69 @@ +From b5e5f9dfc915ff05b41dff56181e1dae101712bd Mon Sep 17 00:00:00 2001 +From: Namjae Jeon +Date: Sun, 19 Jun 2022 22:37:17 +0900 +Subject: ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA + +From: Namjae Jeon + +commit b5e5f9dfc915ff05b41dff56181e1dae101712bd upstream. + +FileOffset should not be greater than BeyondFinalZero in FSCTL_ZERO_DATA. +And don't call ksmbd_vfs_zero_data() if length is zero. + +Cc: stable@vger.kernel.org +Reviewed-by: Hyunchul Lee +Signed-off-by: Namjae Jeon +Signed-off-by: Steve French +Signed-off-by: Greg Kroah-Hartman +--- + fs/ksmbd/smb2pdu.c | 29 ++++++++++++++++++----------- + 1 file changed, 18 insertions(+), 11 deletions(-) + +--- a/fs/ksmbd/smb2pdu.c ++++ b/fs/ksmbd/smb2pdu.c +@@ -7684,7 +7684,7 @@ int smb2_ioctl(struct ksmbd_work *work) + { + struct file_zero_data_information *zero_data; + struct ksmbd_file *fp; +- loff_t off, len; ++ loff_t off, len, bfz; + + if (!test_tree_conn_flag(work->tcon, KSMBD_TREE_CONN_FLAG_WRITABLE)) { + ksmbd_debug(SMB, +@@ -7701,19 +7701,26 @@ int smb2_ioctl(struct ksmbd_work *work) + zero_data = + (struct file_zero_data_information *)&req->Buffer[0]; + +- fp = ksmbd_lookup_fd_fast(work, id); +- if (!fp) { +- ret = -ENOENT; ++ off = le64_to_cpu(zero_data->FileOffset); ++ bfz = le64_to_cpu(zero_data->BeyondFinalZero); ++ if (off > bfz) { ++ ret = -EINVAL; + goto out; + } + +- off = le64_to_cpu(zero_data->FileOffset); +- len = le64_to_cpu(zero_data->BeyondFinalZero) - off; +- +- ret = ksmbd_vfs_zero_data(work, fp, off, len); +- ksmbd_fd_put(work, fp); +- if (ret < 0) +- goto out; ++ len = bfz - off; ++ if (len) { ++ fp = ksmbd_lookup_fd_fast(work, id); ++ if (!fp) { ++ ret = -ENOENT; ++ goto out; ++ } ++ ++ ret = ksmbd_vfs_zero_data(work, fp, off, len); ++ ksmbd_fd_put(work, fp); ++ if (ret < 0) ++ goto out; ++ } + break; + } + case FSCTL_QUERY_ALLOCATED_RANGES: diff --git a/queue-5.15/ksmbd-set-the-range-of-bytes-to-zero-without-extending-file-size-in-fsctl_zero_data.patch b/queue-5.15/ksmbd-set-the-range-of-bytes-to-zero-without-extending-file-size-in-fsctl_zero_data.patch new file mode 100644 index 00000000000..5aeb7d9766a --- /dev/null +++ b/queue-5.15/ksmbd-set-the-range-of-bytes-to-zero-without-extending-file-size-in-fsctl_zero_data.patch @@ -0,0 +1,37 @@ +From 18e39fb960e6a908ac5230b57e3d0d6c25232368 Mon Sep 17 00:00:00 2001 +From: Namjae Jeon +Date: Sun, 19 Jun 2022 22:35:48 +0900 +Subject: ksmbd: set the range of bytes to zero without extending file size in FSCTL_ZERO_DATA + +From: Namjae Jeon + +commit 18e39fb960e6a908ac5230b57e3d0d6c25232368 upstream. + +generic/091, 263 test failed since commit f66f8b94e7f2 ("cifs: when +extending a file with falloc we should make files not-sparse"). +FSCTL_ZERO_DATA sets the range of bytes to zero without extending file +size. The VFS_FALLOCATE_FL_KEEP_SIZE flag should be used even on +non-sparse files. + +Cc: stable@vger.kernel.org +Reviewed-by: Hyunchul Lee +Signed-off-by: Namjae Jeon +Signed-off-by: Steve French +Signed-off-by: Greg Kroah-Hartman +--- + fs/ksmbd/vfs.c | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +--- a/fs/ksmbd/vfs.c ++++ b/fs/ksmbd/vfs.c +@@ -1018,7 +1018,9 @@ int ksmbd_vfs_zero_data(struct ksmbd_wor + FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE, + off, len); + +- return vfs_fallocate(fp->filp, FALLOC_FL_ZERO_RANGE, off, len); ++ return vfs_fallocate(fp->filp, ++ FALLOC_FL_ZERO_RANGE | FALLOC_FL_KEEP_SIZE, ++ off, len); + } + + int ksmbd_vfs_fqar_lseek(struct ksmbd_file *fp, loff_t start, loff_t length, diff --git a/queue-5.15/ksmbd-use-vfs_llseek-instead-of-dereferencing-null.patch b/queue-5.15/ksmbd-use-vfs_llseek-instead-of-dereferencing-null.patch new file mode 100644 index 00000000000..2b558fa28a9 --- /dev/null +++ b/queue-5.15/ksmbd-use-vfs_llseek-instead-of-dereferencing-null.patch @@ -0,0 +1,48 @@ +From 067baa9a37b32b95fdeabccde4b0cb6a2cf95f96 Mon Sep 17 00:00:00 2001 +From: "Jason A. Donenfeld" +Date: Sat, 25 Jun 2022 13:01:08 +0200 +Subject: ksmbd: use vfs_llseek instead of dereferencing NULL + +From: Jason A. Donenfeld + +commit 067baa9a37b32b95fdeabccde4b0cb6a2cf95f96 upstream. + +By not checking whether llseek is NULL, this might jump to NULL. Also, +it doesn't check FMODE_LSEEK. Fix this by using vfs_llseek(), which +always does the right thing. + +Fixes: f44158485826 ("cifsd: add file operations") +Cc: stable@vger.kernel.org +Cc: linux-cifs@vger.kernel.org +Cc: Ronnie Sahlberg +Cc: Hyunchul Lee +Cc: Sergey Senozhatsky +Reviewed-by: Namjae Jeon +Acked-by: Al Viro +Signed-off-by: Jason A. Donenfeld +Signed-off-by: Steve French +Signed-off-by: Greg Kroah-Hartman +--- + fs/ksmbd/vfs.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +--- a/fs/ksmbd/vfs.c ++++ b/fs/ksmbd/vfs.c +@@ -1051,7 +1051,7 @@ int ksmbd_vfs_fqar_lseek(struct ksmbd_fi + *out_count = 0; + end = start + length; + while (start < end && *out_count < in_count) { +- extent_start = f->f_op->llseek(f, start, SEEK_DATA); ++ extent_start = vfs_llseek(f, start, SEEK_DATA); + if (extent_start < 0) { + if (extent_start != -ENXIO) + ret = (int)extent_start; +@@ -1061,7 +1061,7 @@ int ksmbd_vfs_fqar_lseek(struct ksmbd_fi + if (extent_start >= end) + break; + +- extent_end = f->f_op->llseek(f, extent_start, SEEK_HOLE); ++ extent_end = vfs_llseek(f, extent_start, SEEK_HOLE); + if (extent_end < 0) { + if (extent_end != -ENXIO) + ret = (int)extent_end; diff --git a/queue-5.15/net-phy-don-t-trigger-state-machine-while-in-suspend.patch b/queue-5.15/net-phy-don-t-trigger-state-machine-while-in-suspend.patch new file mode 100644 index 00000000000..db0e2abe82d --- /dev/null +++ b/queue-5.15/net-phy-don-t-trigger-state-machine-while-in-suspend.patch @@ -0,0 +1,161 @@ +From 1758bde2e4aa5ff188d53e7d9d388bbb7e12eebb Mon Sep 17 00:00:00 2001 +From: Lukas Wunner +Date: Tue, 28 Jun 2022 12:15:08 +0200 +Subject: net: phy: Don't trigger state machine while in suspend + +From: Lukas Wunner + +commit 1758bde2e4aa5ff188d53e7d9d388bbb7e12eebb upstream. + +Upon system sleep, mdio_bus_phy_suspend() stops the phy_state_machine(), +but subsequent interrupts may retrigger it: + +They may have been left enabled to facilitate wakeup and are not +quiesced until the ->suspend_noirq() phase. Unwanted interrupts may +hence occur between mdio_bus_phy_suspend() and dpm_suspend_noirq(), +as well as between dpm_resume_noirq() and mdio_bus_phy_resume(). + +Retriggering the phy_state_machine() through an interrupt is not only +undesirable for the reason given in mdio_bus_phy_suspend() (freezing it +midway with phydev->lock held), but also because the PHY may be +inaccessible after it's suspended: Accesses to USB-attached PHYs are +blocked once usb_suspend_both() clears the can_submit flag and PHYs on +PCI network cards may become inaccessible upon suspend as well. + +Amend phy_interrupt() to avoid triggering the state machine if the PHY +is suspended. Signal wakeup instead if the attached net_device or its +parent has been configured as a wakeup source. (Those conditions are +identical to mdio_bus_phy_may_suspend().) Postpone handling of the +interrupt until the PHY has resumed. + +Before stopping the phy_state_machine() in mdio_bus_phy_suspend(), +wait for a concurrent phy_interrupt() to run to completion. That is +necessary because phy_interrupt() may have checked the PHY's suspend +status before the system sleep transition commenced and it may thus +retrigger the state machine after it was stopped. + +Likewise, after re-enabling interrupt handling in mdio_bus_phy_resume(), +wait for a concurrent phy_interrupt() to complete to ensure that +interrupts which it postponed are properly rerun. + +The issue was exposed by commit 1ce8b37241ed ("usbnet: smsc95xx: Forward +PHY interrupts to PHY driver to avoid polling"), but has existed since +forever. + +Fixes: 541cd3ee00a4 ("phylib: Fix deadlock on resume") +Link: https://lore.kernel.org/netdev/a5315a8a-32c2-962f-f696-de9a26d30091@samsung.com/ +Reported-by: Marek Szyprowski +Tested-by: Marek Szyprowski +Signed-off-by: Lukas Wunner +Acked-by: Rafael J. Wysocki +Cc: stable@vger.kernel.org # v2.6.33+ +Reviewed-by: Andrew Lunn +Link: https://lore.kernel.org/r/b7f386d04e9b5b0e2738f0125743e30676f309ef.1656410895.git.lukas@wunner.de +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + drivers/net/phy/phy.c | 23 +++++++++++++++++++++++ + drivers/net/phy/phy_device.c | 23 +++++++++++++++++++++++ + include/linux/phy.h | 6 ++++++ + 3 files changed, 52 insertions(+) + +--- a/drivers/net/phy/phy.c ++++ b/drivers/net/phy/phy.c +@@ -31,6 +31,7 @@ + #include + #include + #include ++#include + #include + #include + #include +@@ -972,6 +973,28 @@ static irqreturn_t phy_interrupt(int irq + struct phy_driver *drv = phydev->drv; + irqreturn_t ret; + ++ /* Wakeup interrupts may occur during a system sleep transition. ++ * Postpone handling until the PHY has resumed. ++ */ ++ if (IS_ENABLED(CONFIG_PM_SLEEP) && phydev->irq_suspended) { ++ struct net_device *netdev = phydev->attached_dev; ++ ++ if (netdev) { ++ struct device *parent = netdev->dev.parent; ++ ++ if (netdev->wol_enabled) ++ pm_system_wakeup(); ++ else if (device_may_wakeup(&netdev->dev)) ++ pm_wakeup_dev_event(&netdev->dev, 0, true); ++ else if (parent && device_may_wakeup(parent)) ++ pm_wakeup_dev_event(parent, 0, true); ++ } ++ ++ phydev->irq_rerun = 1; ++ disable_irq_nosync(irq); ++ return IRQ_HANDLED; ++ } ++ + mutex_lock(&phydev->lock); + ret = drv->handle_interrupt(phydev); + mutex_unlock(&phydev->lock); +--- a/drivers/net/phy/phy_device.c ++++ b/drivers/net/phy/phy_device.c +@@ -277,6 +277,15 @@ static __maybe_unused int mdio_bus_phy_s + if (phydev->mac_managed_pm) + return 0; + ++ /* Wakeup interrupts may occur during the system sleep transition when ++ * the PHY is inaccessible. Set flag to postpone handling until the PHY ++ * has resumed. Wait for concurrent interrupt handler to complete. ++ */ ++ if (phy_interrupt_is_valid(phydev)) { ++ phydev->irq_suspended = 1; ++ synchronize_irq(phydev->irq); ++ } ++ + /* We must stop the state machine manually, otherwise it stops out of + * control, possibly with the phydev->lock held. Upon resume, netdev + * may call phy routines that try to grab the same lock, and that may +@@ -314,6 +323,20 @@ static __maybe_unused int mdio_bus_phy_r + if (ret < 0) + return ret; + no_resume: ++ if (phy_interrupt_is_valid(phydev)) { ++ phydev->irq_suspended = 0; ++ synchronize_irq(phydev->irq); ++ ++ /* Rerun interrupts which were postponed by phy_interrupt() ++ * because they occurred during the system sleep transition. ++ */ ++ if (phydev->irq_rerun) { ++ phydev->irq_rerun = 0; ++ enable_irq(phydev->irq); ++ irq_wake_thread(phydev->irq, phydev); ++ } ++ } ++ + if (phydev->attached_dev && phydev->adjust_link) + phy_start_machine(phydev); + +--- a/include/linux/phy.h ++++ b/include/linux/phy.h +@@ -536,6 +536,10 @@ struct macsec_ops; + * @mdix: Current crossover + * @mdix_ctrl: User setting of crossover + * @interrupts: Flag interrupts have been enabled ++ * @irq_suspended: Flag indicating PHY is suspended and therefore interrupt ++ * handling shall be postponed until PHY has resumed ++ * @irq_rerun: Flag indicating interrupts occurred while PHY was suspended, ++ * requiring a rerun of the interrupt handler after resume + * @interface: enum phy_interface_t value + * @skb: Netlink message for cable diagnostics + * @nest: Netlink nest used for cable diagnostics +@@ -590,6 +594,8 @@ struct phy_device { + + /* Interrupts are enabled */ + unsigned interrupts:1; ++ unsigned irq_suspended:1; ++ unsigned irq_rerun:1; + + enum phy_state state; + diff --git a/queue-5.15/nvdimm-fix-badblocks-clear-off-by-one-error.patch b/queue-5.15/nvdimm-fix-badblocks-clear-off-by-one-error.patch new file mode 100644 index 00000000000..9c405c687a6 --- /dev/null +++ b/queue-5.15/nvdimm-fix-badblocks-clear-off-by-one-error.patch @@ -0,0 +1,38 @@ +From ef9102004a87cb3f8b26e000a095a261fc0467d3 Mon Sep 17 00:00:00 2001 +From: Chris Ye +Date: Tue, 31 May 2022 17:09:54 -0700 +Subject: nvdimm: Fix badblocks clear off-by-one error + +From: Chris Ye + +commit ef9102004a87cb3f8b26e000a095a261fc0467d3 upstream. + +nvdimm_clear_badblocks_region() validates badblock clearing requests +against the span of the region, however it compares the inclusive +badblock request range to the exclusive region range. Fix up the +off-by-one error. + +Fixes: 23f498448362 ("libnvdimm: rework region badblocks clearing") +Cc: +Signed-off-by: Chris Ye +Reviewed-by: Vishal Verma +Link: https://lore.kernel.org/r/165404219489.2445897.9792886413715690399.stgit@dwillia2-xfh +Signed-off-by: Dan Williams +Signed-off-by: Greg Kroah-Hartman +--- + drivers/nvdimm/bus.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +--- a/drivers/nvdimm/bus.c ++++ b/drivers/nvdimm/bus.c +@@ -185,8 +185,8 @@ static int nvdimm_clear_badblocks_region + ndr_end = nd_region->ndr_start + nd_region->ndr_size - 1; + + /* make sure we are in the region */ +- if (ctx->phys < nd_region->ndr_start +- || (ctx->phys + ctx->cleared) > ndr_end) ++ if (ctx->phys < nd_region->ndr_start || ++ (ctx->phys + ctx->cleared - 1) > ndr_end) + return 0; + + sector = (ctx->phys - nd_region->ndr_start) / 512; diff --git a/queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-im2p33f8abr1.patch b/queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-im2p33f8abr1.patch new file mode 100644 index 00000000000..1c1a6dca004 --- /dev/null +++ b/queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-im2p33f8abr1.patch @@ -0,0 +1,38 @@ +From e1c70d79346356bb1ede3f79436df80917845ab9 Mon Sep 17 00:00:00 2001 +From: Lamarque Vieira Souza +Date: Wed, 29 Jun 2022 21:30:53 -0300 +Subject: nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Lamarque Vieira Souza + +commit e1c70d79346356bb1ede3f79436df80917845ab9 upstream. + +ADATA IM2P33F8ABR1 reports bogus eui64 values that appear to be the same +across all drives. Quirk them out so they are not marked as "non globally +unique" duplicates. + +Co-developed-by: Felipe de Jesus Araujo da Conceição +Signed-off-by: Felipe de Jesus Araujo da Conceição +Signed-off-by: Lamarque V. Souza +Signed-off-by: Greg Kroah-Hartman + +Cc: stable@vger.kernel.org +Signed-off-by: Christoph Hellwig +--- + drivers/nvme/host/pci.c | 2 ++ + 1 file changed, 2 insertions(+) + +--- a/drivers/nvme/host/pci.c ++++ b/drivers/nvme/host/pci.c +@@ -3341,6 +3341,8 @@ static const struct pci_device_id nvme_i + { PCI_DEVICE(0x1b4b, 0x1092), /* Lexar 256 GB SSD */ + .driver_data = NVME_QUIRK_NO_NS_DESC_LIST | + NVME_QUIRK_IGNORE_DEV_SUBNQN, }, ++ { PCI_DEVICE(0x1cc1, 0x33f8), /* ADATA IM2P33F8ABR1 1 TB */ ++ .driver_data = NVME_QUIRK_BOGUS_NID, }, + { PCI_DEVICE(0x10ec, 0x5762), /* ADATA SX6000LNP */ + .driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN | + NVME_QUIRK_BOGUS_NID, }, diff --git a/queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-xpg-sx6000lnp-aka-spectrix-s40g.patch b/queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-xpg-sx6000lnp-aka-spectrix-s40g.patch new file mode 100644 index 00000000000..f84317d170b --- /dev/null +++ b/queue-5.15/nvme-pci-add-nvme_quirk_bogus_nid-for-adata-xpg-sx6000lnp-aka-spectrix-s40g.patch @@ -0,0 +1,59 @@ +From 1629de0e0373e04d68e88e6d9d3071fbf70b7ea8 Mon Sep 17 00:00:00 2001 +From: Pablo Greco +Date: Sat, 25 Jun 2022 09:15:02 -0300 +Subject: nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX S40G) + +From: Pablo Greco + +commit 1629de0e0373e04d68e88e6d9d3071fbf70b7ea8 upstream. + +ADATA XPG SPECTRIX S40G drives report bogus eui64 values that appear to +be the same across drives in one system. Quirk them out so they are +not marked as "non globally unique" duplicates. + +Before: +[ 2.258919] nvme nvme1: pci function 0000:06:00.0 +[ 2.264898] nvme nvme2: pci function 0000:05:00.0 +[ 2.323235] nvme nvme1: failed to set APST feature (2) +[ 2.326153] nvme nvme2: failed to set APST feature (2) +[ 2.333935] nvme nvme1: allocated 64 MiB host memory buffer. +[ 2.336492] nvme nvme2: allocated 64 MiB host memory buffer. +[ 2.339611] nvme nvme1: 7/0/0 default/read/poll queues +[ 2.341805] nvme nvme2: 7/0/0 default/read/poll queues +[ 2.346114] nvme1n1: p1 +[ 2.347197] nvme nvme2: globally duplicate IDs for nsid 1 +After: +[ 2.427715] nvme nvme1: pci function 0000:06:00.0 +[ 2.427771] nvme nvme2: pci function 0000:05:00.0 +[ 2.488154] nvme nvme2: failed to set APST feature (2) +[ 2.489895] nvme nvme1: failed to set APST feature (2) +[ 2.498773] nvme nvme2: allocated 64 MiB host memory buffer. +[ 2.500587] nvme nvme1: allocated 64 MiB host memory buffer. +[ 2.504113] nvme nvme2: 7/0/0 default/read/poll queues +[ 2.507026] nvme nvme1: 7/0/0 default/read/poll queues +[ 2.509467] nvme nvme2: Ignoring bogus Namespace Identifiers +[ 2.512804] nvme nvme1: Ignoring bogus Namespace Identifiers +[ 2.513698] nvme1n1: p1 + +Signed-off-by: Pablo Greco +Reviewed-by: Keith Busch +Reviewed-by: Chaitanya Kulkarni +Cc: +Signed-off-by: Christoph Hellwig +Signed-off-by: Greg Kroah-Hartman +--- + drivers/nvme/host/pci.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +--- a/drivers/nvme/host/pci.c ++++ b/drivers/nvme/host/pci.c +@@ -3342,7 +3342,8 @@ static const struct pci_device_id nvme_i + .driver_data = NVME_QUIRK_NO_NS_DESC_LIST | + NVME_QUIRK_IGNORE_DEV_SUBNQN, }, + { PCI_DEVICE(0x10ec, 0x5762), /* ADATA SX6000LNP */ +- .driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN, }, ++ .driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN | ++ NVME_QUIRK_BOGUS_NID, }, + { PCI_DEVICE(0x1cc1, 0x8201), /* ADATA SX8200PNP 512GB */ + .driver_data = NVME_QUIRK_NO_DEEPEST_PS | + NVME_QUIRK_IGNORE_DEV_SUBNQN, }, diff --git a/queue-5.15/powerpc-book3e-fix-pud-allocation-size-in-map_kernel_page.patch b/queue-5.15/powerpc-book3e-fix-pud-allocation-size-in-map_kernel_page.patch new file mode 100644 index 00000000000..4b1eb2dacac --- /dev/null +++ b/queue-5.15/powerpc-book3e-fix-pud-allocation-size-in-map_kernel_page.patch @@ -0,0 +1,48 @@ +From 986481618023e18e187646b0fff05a3c337531cb Mon Sep 17 00:00:00 2001 +From: Christophe Leroy +Date: Thu, 23 Jun 2022 10:56:17 +0200 +Subject: powerpc/book3e: Fix PUD allocation size in map_kernel_page() + +From: Christophe Leroy + +commit 986481618023e18e187646b0fff05a3c337531cb upstream. + +Commit 2fb4706057bc ("powerpc: add support for folded p4d page tables") +erroneously changed PUD setup to a mix of PMD and PUD. Fix it. + +While at it, use PTE_TABLE_SIZE instead of PAGE_SIZE for PTE tables +in order to avoid any confusion. + +Fixes: 2fb4706057bc ("powerpc: add support for folded p4d page tables") +Cc: stable@vger.kernel.org # v5.8+ +Signed-off-by: Christophe Leroy +Acked-by: Mike Rapoport +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/95ddfd6176d53e6c85e13bd1c358359daa56775f.1655974558.git.christophe.leroy@csgroup.eu +Signed-off-by: Greg Kroah-Hartman +--- + arch/powerpc/mm/nohash/book3e_pgtable.c | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +--- a/arch/powerpc/mm/nohash/book3e_pgtable.c ++++ b/arch/powerpc/mm/nohash/book3e_pgtable.c +@@ -95,8 +95,8 @@ int __ref map_kernel_page(unsigned long + pgdp = pgd_offset_k(ea); + p4dp = p4d_offset(pgdp, ea); + if (p4d_none(*p4dp)) { +- pmdp = early_alloc_pgtable(PMD_TABLE_SIZE); +- p4d_populate(&init_mm, p4dp, pmdp); ++ pudp = early_alloc_pgtable(PUD_TABLE_SIZE); ++ p4d_populate(&init_mm, p4dp, pudp); + } + pudp = pud_offset(p4dp, ea); + if (pud_none(*pudp)) { +@@ -105,7 +105,7 @@ int __ref map_kernel_page(unsigned long + } + pmdp = pmd_offset(pudp, ea); + if (!pmd_present(*pmdp)) { +- ptep = early_alloc_pgtable(PAGE_SIZE); ++ ptep = early_alloc_pgtable(PTE_TABLE_SIZE); + pmd_populate_kernel(&init_mm, pmdp, ptep); + } + ptep = pte_offset_kernel(pmdp, ea); diff --git a/queue-5.15/powerpc-bpf-fix-use-of-user_pt_regs-in-uapi.patch b/queue-5.15/powerpc-bpf-fix-use-of-user_pt_regs-in-uapi.patch new file mode 100644 index 00000000000..49c65db9f6c --- /dev/null +++ b/queue-5.15/powerpc-bpf-fix-use-of-user_pt_regs-in-uapi.patch @@ -0,0 +1,81 @@ +From b21bd5a4b130f8370861478d2880985daace5913 Mon Sep 17 00:00:00 2001 +From: "Naveen N. Rao" +Date: Tue, 28 Jun 2022 00:41:19 +0530 +Subject: powerpc/bpf: Fix use of user_pt_regs in uapi +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Naveen N. Rao + +commit b21bd5a4b130f8370861478d2880985daace5913 upstream. + +Trying to build a .c file that includes : + $ cat test_bpf_headers.c + #include + +throws the below error: + /usr/include/linux/bpf_perf_event.h:14:28: error: field ‘regs’ has incomplete type + 14 | bpf_user_pt_regs_t regs; + | ^~~~ + +This is because we typedef bpf_user_pt_regs_t to 'struct user_pt_regs' +in arch/powerpc/include/uaps/asm/bpf_perf_event.h, but 'struct +user_pt_regs' is not exposed to userspace. + +Powerpc has both pt_regs and user_pt_regs structures. However, unlike +arm64 and s390, we expose user_pt_regs to userspace as just 'pt_regs'. +As such, we should typedef bpf_user_pt_regs_t to 'struct pt_regs' for +userspace. + +Within the kernel though, we want to typedef bpf_user_pt_regs_t to +'struct user_pt_regs'. + +Remove arch/powerpc/include/uapi/asm/bpf_perf_event.h so that the +uapi/asm-generic version of the header is exposed to userspace. +Introduce arch/powerpc/include/asm/bpf_perf_event.h so that we can +typedef bpf_user_pt_regs_t to 'struct user_pt_regs' for use within the +kernel. + +Note that this was not showing up with the bpf selftest build since +tools/include/uapi/asm/bpf_perf_event.h didn't include the powerpc +variant. + +Fixes: a6460b03f945ee ("powerpc/bpf: Fix broken uapi for BPF_PROG_TYPE_PERF_EVENT") +Cc: stable@vger.kernel.org # v4.20+ +Signed-off-by: Naveen N. Rao +[mpe: Use typical naming for header include guard] +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/20220627191119.142867-1-naveen.n.rao@linux.vnet.ibm.com +Signed-off-by: Greg Kroah-Hartman +--- + arch/powerpc/include/asm/bpf_perf_event.h | 9 +++++++++ + arch/powerpc/include/uapi/asm/bpf_perf_event.h | 9 --------- + 2 files changed, 9 insertions(+), 9 deletions(-) + create mode 100644 arch/powerpc/include/asm/bpf_perf_event.h + delete mode 100644 arch/powerpc/include/uapi/asm/bpf_perf_event.h + +--- /dev/null ++++ b/arch/powerpc/include/asm/bpf_perf_event.h +@@ -0,0 +1,9 @@ ++/* SPDX-License-Identifier: GPL-2.0 */ ++#ifndef _ASM_POWERPC_BPF_PERF_EVENT_H ++#define _ASM_POWERPC_BPF_PERF_EVENT_H ++ ++#include ++ ++typedef struct user_pt_regs bpf_user_pt_regs_t; ++ ++#endif /* _ASM_POWERPC_BPF_PERF_EVENT_H */ +--- a/arch/powerpc/include/uapi/asm/bpf_perf_event.h ++++ /dev/null +@@ -1,9 +0,0 @@ +-/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */ +-#ifndef _UAPI__ASM_BPF_PERF_EVENT_H__ +-#define _UAPI__ASM_BPF_PERF_EVENT_H__ +- +-#include +- +-typedef struct user_pt_regs bpf_user_pt_regs_t; +- +-#endif /* _UAPI__ASM_BPF_PERF_EVENT_H__ */ diff --git a/queue-5.15/powerpc-prom_init-fix-kernel-config-grep.patch b/queue-5.15/powerpc-prom_init-fix-kernel-config-grep.patch new file mode 100644 index 00000000000..636dbe10604 --- /dev/null +++ b/queue-5.15/powerpc-prom_init-fix-kernel-config-grep.patch @@ -0,0 +1,33 @@ +From 6886da5f49e6d86aad76807a93f3eef5e4f01b10 Mon Sep 17 00:00:00 2001 +From: Liam Howlett +Date: Fri, 24 Jun 2022 01:17:58 +0000 +Subject: powerpc/prom_init: Fix kernel config grep + +From: Liam Howlett + +commit 6886da5f49e6d86aad76807a93f3eef5e4f01b10 upstream. + +When searching for config options, use the KCONFIG_CONFIG shell variable +so that builds using non-standard config locations work. + +Fixes: 26deb04342e3 ("powerpc: prepare string/mem functions for KASAN") +Cc: stable@vger.kernel.org # v5.2+ +Signed-off-by: Liam R. Howlett +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/20220624011745.4060795-1-Liam.Howlett@oracle.com +Signed-off-by: Greg Kroah-Hartman +--- + arch/powerpc/kernel/prom_init_check.sh | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/arch/powerpc/kernel/prom_init_check.sh ++++ b/arch/powerpc/kernel/prom_init_check.sh +@@ -13,7 +13,7 @@ + # If you really need to reference something from prom_init.o add + # it to the list below: + +-grep "^CONFIG_KASAN=y$" .config >/dev/null ++grep "^CONFIG_KASAN=y$" ${KCONFIG_CONFIG} >/dev/null + if [ $? -eq 0 ] + then + MEM_FUNCS="__memcpy __memset" diff --git a/queue-5.15/revert-drm-amdgpu-display-set-vblank_disable_immediate-for-dc.patch b/queue-5.15/revert-drm-amdgpu-display-set-vblank_disable_immediate-for-dc.patch new file mode 100644 index 00000000000..02f3de43799 --- /dev/null +++ b/queue-5.15/revert-drm-amdgpu-display-set-vblank_disable_immediate-for-dc.patch @@ -0,0 +1,48 @@ +From a775e4e4941bf2f326aa36c58f67bd6c96cac717 Mon Sep 17 00:00:00 2001 +From: Alex Deucher +Date: Mon, 20 Jun 2022 18:29:39 -0400 +Subject: Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" + +From: Alex Deucher + +commit a775e4e4941bf2f326aa36c58f67bd6c96cac717 upstream. + +This reverts commit 92020e81ddbeac351ea4a19bcf01743f32b9c800. + +This causes stuttering and timeouts with DMCUB for some users +so revert it until we understand why and safely enable it +to save power. + +Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1887 +Acked-by: Harry Wentland +Signed-off-by: Alex Deucher +Cc: Nicholas Kazlauskas +Cc: stable@vger.kernel.org +Signed-off-by: Greg Kroah-Hartman +--- + drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c | 1 + + drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3 --- + 2 files changed, 1 insertion(+), 3 deletions(-) + +--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c ++++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c +@@ -333,6 +333,7 @@ int amdgpu_irq_init(struct amdgpu_device + if (!amdgpu_device_has_dc_support(adev)) { + if (!adev->enable_virtual_display) + /* Disable vblank IRQs aggressively for power-saving */ ++ /* XXX: can this be enabled for DC? */ + adev_to_drm(adev)->vblank_disable_immediate = true; + + r = drm_vblank_init(adev_to_drm(adev), adev->mode_info.num_crtc); +--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c ++++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +@@ -3838,9 +3838,6 @@ static int amdgpu_dm_initialize_drm_devi + } + #endif + +- /* Disable vblank IRQs aggressively for power-saving. */ +- adev_to_drm(adev)->vblank_disable_immediate = true; +- + /* loops over all connectors on the board */ + for (i = 0; i < link_cnt; i++) { + struct dc_link *link = NULL; diff --git a/queue-5.15/series b/queue-5.15/series new file mode 100644 index 00000000000..16e578eac6f --- /dev/null +++ b/queue-5.15/series @@ -0,0 +1,15 @@ +revert-drm-amdgpu-display-set-vblank_disable_immediate-for-dc.patch +drm-amdgpu-to-flush-tlb-for-mmhub-of-raven-series.patch +ksmbd-set-the-range-of-bytes-to-zero-without-extending-file-size-in-fsctl_zero_data.patch +ksmbd-check-invalid-fileoffset-and-beyondfinalzero-in-fsctl_zero_data.patch +ksmbd-use-vfs_llseek-instead-of-dereferencing-null.patch +ipv6-take-care-of-disable_policy-when-restoring-routes.patch +net-phy-don-t-trigger-state-machine-while-in-suspend.patch +nvme-pci-add-nvme_quirk_bogus_nid-for-adata-xpg-sx6000lnp-aka-spectrix-s40g.patch +nvme-pci-add-nvme_quirk_bogus_nid-for-adata-im2p33f8abr1.patch +nvdimm-fix-badblocks-clear-off-by-one-error.patch +powerpc-prom_init-fix-kernel-config-grep.patch +powerpc-book3e-fix-pud-allocation-size-in-map_kernel_page.patch +powerpc-bpf-fix-use-of-user_pt_regs-in-uapi.patch +dm-raid-fix-accesses-beyond-end-of-raid-member-array.patch +dm-raid-fix-kasan-warning-in-raid5_add_disks.patch -- 2.47.3