Public bug reported:

[ Impact ]

 * Boot hangs because of deadlock caused by mm (memory management)
   during CPU bring-up.

[ Fix ]

 * Upstream commit :
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49

[ Test Plan ]

 * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
   since its appearance frequency has been increased by the introduction of 
another commit
   for fixing an unrelated issue when booting a large memory profile TDX VM.
   
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)

   Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
   with a certain CPU configuration:

   For AMD SNP,  you can follow the instructions in the submission
   https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t

   For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 
6.14 -intel kernel that has
   TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).

[ Where problems could occur ]

 * Problems could occur during system boot and CPU bring up

[ Further information ]

 * It is necessary to backport this patch to Plucky and Oracular kernel since
   the commit that exhibits this deadlock is in Plucky 6.14 and being backported
   to Oracular 6.11 kernel (currently the patch lives in master-next as of 
   today Apr 29th). 
   (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530)

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux-intel (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Description changed:

  [ Impact ]
  
-  * Boot hangs because of deadlock caused by mm (memory management)
-    during CPU bring-up.
-  
+  * Boot hangs because of deadlock caused by mm (memory management)
+    during CPU bring-up.
+ 
  [ Fix ]
  
-  * Upstream commit :
-    
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49
+  * Upstream commit :
+    
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49
  
  [ Test Plan ]
  
-  * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
-    since its appearance frequency has been increased by the introduction of 
another commit
-    for fixing an unrelated issue when booting a large memory profile TDX VM.
-    
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)
 
+  * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
+    since its appearance frequency has been increased by the introduction of 
another commit
+    for fixing an unrelated issue when booting a large memory profile TDX VM.
+    
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)
  
-    Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
-    with a certain CPU configuration:
-    
-    For AMD SNP,  you can follow the instructions in the submission
-    https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t
-  
-    We can also reproduce this issue with Intel TDX VM with our 6.14 -intel 
kernel that has
-    TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).
+    Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
+    with a certain CPU configuration:
+ 
+    For AMD SNP,  you can follow the instructions in the submission
+    https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t
+ 
+    For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 
6.14 -intel kernel that has
+    TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).
  
  [ Where problems could occur ]
  
-  * Problems could occur during system boot and CPU bring up
+  * Problems could occur during system boot and CPU bring up

** Description changed:

  [ Impact ]
  
   * Boot hangs because of deadlock caused by mm (memory management)
     during CPU bring-up.
  
  [ Fix ]
  
   * Upstream commit :
     
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49
  
  [ Test Plan ]
  
   * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
     since its appearance frequency has been increased by the introduction of 
another commit
     for fixing an unrelated issue when booting a large memory profile TDX VM.
     
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)
  
     Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
     with a certain CPU configuration:
  
     For AMD SNP,  you can follow the instructions in the submission
     https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t
  
     For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 
6.14 -intel kernel that has
     TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).
  
  [ Where problems could occur ]
  
   * Problems could occur during system boot and CPU bring up
+ 
+ [ Further information ]
+ 
+  * It is necessary to backport this patch to Plucky and Oracular kernel since 
+    the commit that exhibits this deadlock is in Plucky and being backported 
to 
+    Oracular
+    (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530)

** Description changed:

  [ Impact ]
  
   * Boot hangs because of deadlock caused by mm (memory management)
     during CPU bring-up.
  
  [ Fix ]
  
   * Upstream commit :
     
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49
  
  [ Test Plan ]
  
   * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
     since its appearance frequency has been increased by the introduction of 
another commit
     for fixing an unrelated issue when booting a large memory profile TDX VM.
     
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)
  
     Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
     with a certain CPU configuration:
  
     For AMD SNP,  you can follow the instructions in the submission
     https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t
  
     For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 
6.14 -intel kernel that has
     TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).
  
  [ Where problems could occur ]
  
   * Problems could occur during system boot and CPU bring up
  
  [ Further information ]
  
-  * It is necessary to backport this patch to Plucky and Oracular kernel since 
-    the commit that exhibits this deadlock is in Plucky and being backported 
to 
-    Oracular
-    (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530)
+  * It is necessary to backport this patch to Plucky and Oracular kernel since
+    the commit that exhibits this deadlock is in Plucky 6.14 and being 
backported 
+    to Oracular 6.8 kernel
+    (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530)

** Description changed:

  [ Impact ]
  
   * Boot hangs because of deadlock caused by mm (memory management)
     during CPU bring-up.
  
  [ Fix ]
  
   * Upstream commit :
     
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49
  
  [ Test Plan ]
  
   * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
     since its appearance frequency has been increased by the introduction of 
another commit
     for fixing an unrelated issue when booting a large memory profile TDX VM.
     
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)
  
     Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
     with a certain CPU configuration:
  
     For AMD SNP,  you can follow the instructions in the submission
     https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t
  
     For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 
6.14 -intel kernel that has
     TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).
  
  [ Where problems could occur ]
  
   * Problems could occur during system boot and CPU bring up
  
  [ Further information ]
  
   * It is necessary to backport this patch to Plucky and Oracular kernel since
-    the commit that exhibits this deadlock is in Plucky 6.14 and being 
backported 
-    to Oracular 6.8 kernel
+    the commit that exhibits this deadlock is in Plucky 6.14 and being 
backported
+    to Oracular 6.11 kernel
     (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530)

** Description changed:

  [ Impact ]
  
   * Boot hangs because of deadlock caused by mm (memory management)
     during CPU bring-up.
  
  [ Fix ]
  
   * Upstream commit :
     
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49
  
  [ Test Plan ]
  
   * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
     since its appearance frequency has been increased by the introduction of 
another commit
     for fixing an unrelated issue when booting a large memory profile TDX VM.
     
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)
  
     Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
     with a certain CPU configuration:
  
     For AMD SNP,  you can follow the instructions in the submission
     https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t
  
     For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 
6.14 -intel kernel that has
     TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).
  
  [ Where problems could occur ]
  
   * Problems could occur during system boot and CPU bring up
  
  [ Further information ]
  
   * It is necessary to backport this patch to Plucky and Oracular kernel since
     the commit that exhibits this deadlock is in Plucky 6.14 and being 
backported
-    to Oracular 6.11 kernel
+    to Oracular 6.11 kernel (currently the patch lives in master-next as of 
+    today Apr 29th). 
     (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2109543

Title:
  deadlock on cpu_hotplug_lock in __accept_page()

Status in linux package in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * Boot hangs because of deadlock caused by mm (memory management)
     during CPU bring-up.

  [ Fix ]

   * Upstream commit :
     
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49

  [ Test Plan ]

   * This deadlock has been uncovered in the context of confidential VMs work 
(AMD SNP & TDX)
     since its appearance frequency has been increased by the introduction of 
another commit
     for fixing an unrelated issue when booting a large memory profile TDX VM.
     
(https://lore.kernel.org/all/20250310082855.2587122-1-kirill.shute...@linux.intel.com/#t)

     Per consequence, to have a better chance to reproduce the issue, run a AMD 
SNP or TDX VM
     with a certain CPU configuration:

     For AMD SNP,  you can follow the instructions in the submission
     https://lore.kernel.org/all/363f8293-23e3-44d3-8005-b31eb5b7f...@amd.com/#t

     For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 
6.14 -intel kernel that has
     TDX feature enabled (since TDX feature is only in kernel main-next for now 
and not yet released).

  [ Where problems could occur ]

   * Problems could occur during system boot and CPU bring up

  [ Further information ]

   * It is necessary to backport this patch to Plucky and Oracular kernel since
     the commit that exhibits this deadlock is in Plucky 6.14 and being 
backported
     to Oracular 6.11 kernel (currently the patch lives in master-next as of 
     today Apr 29th). 
     (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109543/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to