Skip to content

cdrom: patch for inclusion#53

Closed
blktests-ci[bot] wants to merge 0 commit intolinus-master_basefrom
series/984923=>linus-master
Closed

cdrom: patch for inclusion#53
blktests-ci[bot] wants to merge 0 commit intolinus-master_basefrom
series/984923=>linus-master

Conversation

@blktests-ci
Copy link
Copy Markdown

@blktests-ci blktests-ci Bot commented Jul 23, 2025

Pull request for series with
subject: cdrom: patch for inclusion
version: 1
url: https://patchwork.kernel.org/project/linux-block/list/?series=984923

@blktests-ci
Copy link
Copy Markdown
Author

blktests-ci Bot commented Jul 23, 2025

Upstream branch: 89be9a8
series: https://patchwork.kernel.org/project/linux-block/list/?series=984923
version: 1

@blktests-ci
Copy link
Copy Markdown
Author

blktests-ci Bot commented Jul 24, 2025

Upstream branch: 25fae0b
series: https://patchwork.kernel.org/project/linux-block/list/?series=984923
version: 1

@blktests-ci blktests-ci Bot force-pushed the series/984923=>linus-master branch from 12b4c19 to d318d06 Compare July 24, 2025 06:46
@blktests-ci blktests-ci Bot force-pushed the linus-master_base branch 2 times, most recently from 6637119 to f092a9b Compare July 31, 2025 04:25
@blktests-ci
Copy link
Copy Markdown
Author

blktests-ci Bot commented Jul 31, 2025

Upstream branch: 260f6f4
series: https://patchwork.kernel.org/project/linux-block/list/?series=984923
version: 1

@blktests-ci blktests-ci Bot closed this Jul 31, 2025
@blktests-ci blktests-ci Bot force-pushed the series/984923=>linus-master branch from d318d06 to f092a9b Compare July 31, 2025 04:33
@blktests-ci blktests-ci Bot deleted the series/984923=>linus-master branch August 1, 2025 19:36
blktests-ci Bot pushed a commit that referenced this pull request Nov 16, 2025
The following lockdep splat was observed while kernel auto-online a CXL
memory region:

======================================================
WARNING: possible circular locking dependency detected
6.17.0djtest+ #53 Tainted: G        W
------------------------------------------------------
systemd-udevd/3334 is trying to acquire lock:
ffffffff90346188 (hmem_resource_lock){+.+.}-{4:4}, at: hmem_register_resource+0x31/0x50

but task is already holding lock:
ffffffff90338890 ((node_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x2e/0x70

which lock already depends on the new lock.
[..]
Chain exists of:
  hmem_resource_lock --> mem_hotplug_lock --> (node_chain).rwsem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock((node_chain).rwsem);
                               lock(mem_hotplug_lock);
                               lock((node_chain).rwsem);
  lock(hmem_resource_lock);

The lock ordering can cause potential deadlock. There are instances
where hmem_resource_lock is taken after (node_chain).rwsem, and vice
versa.

Split out the target update section of hmat_register_target() so that
hmat_callback() only envokes that section instead of attempt to register
hmem devices that it does not need to.

[ dj: Fix up comment to be closer to 80cols. (Jonathan) ]

Fixes: cf8741a ("ACPI: NUMA: HMAT: Register "soft reserved" memory as an "hmem" device")
Reviewed-by: Jonathan Cameron <[email protected]>
Tested-by: Smita Koralahalli <[email protected]>
Reviewed-by: Smita Koralahalli <[email protected]>
Reviewed-by: Dan Williams <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Dave Jiang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants