* [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type
@ 2023-06-26 15:13 Jason Gunthorpe
2023-06-27 5:50 ` Tian, Kevin
` (3 more replies)
0 siblings, 4 replies; 6+ messages in thread
From: Jason Gunthorpe @ 2023-06-26 15:13 UTC (permalink / raw)
To: iommu, Joerg Roedel, Robin Murphy, Will Deacon
Cc: Lu Baolu, Dheeraj Kumar Srivastava, Heiko Stuebner, Joerg Roedel,
Kevin Tian, Niklas Schnelle, Vasant Hegde
The err_restore_domain flow was accidently inserted into the success path
in commit 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on
ARM"). It should only happen if iommu_create_device_direct_mappings()
fails. This caused the domains the be wrongly changed and freed whenever
the sysfs is used, resulting in an oops:
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 1 PID: 3417 Comm: avocado Not tainted 6.4.0-rc4-next-20230602 #3
Hardware name: Dell Inc. PowerEdge R6515/07PXPY, BIOS 2.3.6 07/06/2021
RIP: 0010:__iommu_attach_device+0xc/0xa0
Code: c0 c3 cc cc cc cc 48 89 f0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 41 54 55 48 8b 47 08 <48> 8b 00 48 85 c0 74 74 48 89 f5 e8 64 12 49 00 41 89 c4 85 c0 74
RSP: 0018:ffffabae0220bd48 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff9ac04f70e410 RCX: 0000000000000001
RDX: ffff9ac044db20c0 RSI: ffff9ac044fa50d0 RDI: ffff9ac04f70e410
RBP: ffff9ac044fa50d0 R08: 1000000100209001 R09: 00000000000002dc
R10: 0000000000000000 R11: 0000000000000000 R12: ffff9ac043d54700
R13: ffff9ac043d54700 R14: 0000000000000001 R15: 0000000000000001
FS: 00007f02e30ae000(0000) GS:ffff9afeb2440000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000012afca006 CR4: 0000000000770ee0
PKRU: 55555554
Call Trace:
<TASK>
? __die+0x24/0x70
? page_fault_oops+0x82/0x150
? __iommu_queue_command_sync+0x80/0xc0
? exc_page_fault+0x69/0x150
? asm_exc_page_fault+0x26/0x30
? __iommu_attach_device+0xc/0xa0
? __iommu_attach_device+0x1c/0xa0
__iommu_device_set_domain+0x42/0x80
__iommu_group_set_domain_internal+0x5d/0x160
iommu_setup_default_domain+0x318/0x400
iommu_group_store_type+0xb1/0x200
kernfs_fop_write_iter+0x12f/0x1c0
vfs_write+0x2a2/0x3b0
ksys_write+0x63/0xe0
do_syscall_64+0x3f/0x90
entry_SYSCALL_64_after_hwframe+0x6e/0xd8
RIP: 0033:0x7f02e2f14a6f
Reorganize the error flow so that the success branch and error branches
are clearer.
Cc: <stable@vger.kernel.org>
Fixes: 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on ARM")
Reported-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
Tested-by: Vasant Hegde <vasant.hegde@amd.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
drivers/iommu/iommu.c | 31 ++++++++++++++++---------------
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index 9e0228ef612b85..36d64662cb21ae 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -2891,14 +2891,11 @@ static int iommu_setup_default_domain(struct iommu_group *group,
ret = __iommu_group_set_domain_internal(
group, dom, IOMMU_SET_DOMAIN_MUST_SUCCEED);
if (WARN_ON(ret))
- goto out_free;
+ goto out_free_old;
} else {
ret = __iommu_group_set_domain(group, dom);
- if (ret) {
- iommu_domain_free(dom);
- group->default_domain = old_dom;
- return ret;
- }
+ if (ret)
+ goto err_restore_def_domain;
}
/*
@@ -2911,21 +2908,25 @@ static int iommu_setup_default_domain(struct iommu_group *group,
for_each_group_device(group, gdev) {
ret = iommu_create_device_direct_mappings(dom, gdev->dev);
if (ret)
- goto err_restore;
+ goto err_restore_domain;
}
}
-err_restore:
- if (old_dom) {
- __iommu_group_set_domain_internal(
- group, old_dom, IOMMU_SET_DOMAIN_MUST_SUCCEED);
- iommu_domain_free(dom);
- old_dom = NULL;
- }
-out_free:
+out_free_old:
if (old_dom)
iommu_domain_free(old_dom);
return ret;
+
+err_restore_domain:
+ if (old_dom)
+ __iommu_group_set_domain_internal(
+ group, old_dom, IOMMU_SET_DOMAIN_MUST_SUCCEED);
+err_restore_def_domain:
+ if (old_dom) {
+ iommu_domain_free(dom);
+ group->default_domain = old_dom;
+ }
+ return ret;
}
/*
base-commit: 8553205b97bad79174137f3fe832fb328947e067
--
2.40.1
^ permalink raw reply related [flat|nested] 6+ messages in thread
* RE: [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type
2023-06-26 15:13 [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type Jason Gunthorpe
@ 2023-06-27 5:50 ` Tian, Kevin
2023-06-27 7:43 ` Baolu Lu
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: Tian, Kevin @ 2023-06-27 5:50 UTC (permalink / raw)
To: Jason Gunthorpe, iommu, Joerg Roedel, Robin Murphy, Will Deacon
Cc: Lu Baolu, Dheeraj Kumar Srivastava, Heiko Stuebner, Rodel, Jorg,
Niklas Schnelle, Vasant Hegde
> From: Jason Gunthorpe <jgg@nvidia.com>
> Sent: Monday, June 26, 2023 11:13 PM
>
> The err_restore_domain flow was accidently inserted into the success path
> in commit 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on
> ARM"). It should only happen if iommu_create_device_direct_mappings()
> fails. This caused the domains the be wrongly changed and freed whenever
> the sysfs is used, resulting in an oops:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 0 P4D 0
> Oops: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 1 PID: 3417 Comm: avocado Not tainted 6.4.0-rc4-next-20230602 #3
> Hardware name: Dell Inc. PowerEdge R6515/07PXPY, BIOS 2.3.6 07/06/2021
> RIP: 0010:__iommu_attach_device+0xc/0xa0
> Code: c0 c3 cc cc cc cc 48 89 f0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90
> 90 90 90 90 90 0f 1f 44 00 00 41 54 55 48 8b 47 08 <48> 8b 00 48 85 c0 74 74
> 48 89 f5 e8 64 12 49 00 41 89 c4 85 c0 74
> RSP: 0018:ffffabae0220bd48 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffff9ac04f70e410 RCX: 0000000000000001
> RDX: ffff9ac044db20c0 RSI: ffff9ac044fa50d0 RDI: ffff9ac04f70e410
> RBP: ffff9ac044fa50d0 R08: 1000000100209001 R09: 00000000000002dc
> R10: 0000000000000000 R11: 0000000000000000 R12: ffff9ac043d54700
> R13: ffff9ac043d54700 R14: 0000000000000001 R15: 0000000000000001
> FS: 00007f02e30ae000(0000) GS:ffff9afeb2440000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 000000012afca006 CR4: 0000000000770ee0
> PKRU: 55555554
> Call Trace:
> <TASK>
> ? __die+0x24/0x70
> ? page_fault_oops+0x82/0x150
> ? __iommu_queue_command_sync+0x80/0xc0
> ? exc_page_fault+0x69/0x150
> ? asm_exc_page_fault+0x26/0x30
> ? __iommu_attach_device+0xc/0xa0
> ? __iommu_attach_device+0x1c/0xa0
> __iommu_device_set_domain+0x42/0x80
> __iommu_group_set_domain_internal+0x5d/0x160
> iommu_setup_default_domain+0x318/0x400
> iommu_group_store_type+0xb1/0x200
> kernfs_fop_write_iter+0x12f/0x1c0
> vfs_write+0x2a2/0x3b0
> ksys_write+0x63/0xe0
> do_syscall_64+0x3f/0x90
> entry_SYSCALL_64_after_hwframe+0x6e/0xd8
> RIP: 0033:0x7f02e2f14a6f
>
> Reorganize the error flow so that the success branch and error branches
> are clearer.
>
> Cc: <stable@vger.kernel.org>
> Fixes: 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on
> ARM")
> Reported-by: Dheeraj Kumar Srivastava
> <dheerajkumar.srivastava@amd.com>
> Tested-by: Vasant Hegde <vasant.hegde@amd.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type
2023-06-26 15:13 [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type Jason Gunthorpe
2023-06-27 5:50 ` Tian, Kevin
@ 2023-06-27 7:43 ` Baolu Lu
2023-07-07 8:30 ` Joerg Roedel
2023-07-14 12:49 ` Joerg Roedel
3 siblings, 0 replies; 6+ messages in thread
From: Baolu Lu @ 2023-06-27 7:43 UTC (permalink / raw)
To: Jason Gunthorpe, iommu, Joerg Roedel, Robin Murphy, Will Deacon
Cc: baolu.lu, Dheeraj Kumar Srivastava, Heiko Stuebner, Joerg Roedel,
Kevin Tian, Niklas Schnelle, Vasant Hegde
On 2023/6/26 23:13, Jason Gunthorpe wrote:
> The err_restore_domain flow was accidently inserted into the success path
> in commit 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on
> ARM"). It should only happen if iommu_create_device_direct_mappings()
> fails. This caused the domains the be wrongly changed and freed whenever
minor: ...caused the domains to be wrongly changed...
> the sysfs is used, resulting in an oops:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 0 P4D 0
> Oops: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 1 PID: 3417 Comm: avocado Not tainted 6.4.0-rc4-next-20230602 #3
> Hardware name: Dell Inc. PowerEdge R6515/07PXPY, BIOS 2.3.6 07/06/2021
> RIP: 0010:__iommu_attach_device+0xc/0xa0
> Code: c0 c3 cc cc cc cc 48 89 f0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 41 54 55 48 8b 47 08 <48> 8b 00 48 85 c0 74 74 48 89 f5 e8 64 12 49 00 41 89 c4 85 c0 74
> RSP: 0018:ffffabae0220bd48 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffff9ac04f70e410 RCX: 0000000000000001
> RDX: ffff9ac044db20c0 RSI: ffff9ac044fa50d0 RDI: ffff9ac04f70e410
> RBP: ffff9ac044fa50d0 R08: 1000000100209001 R09: 00000000000002dc
> R10: 0000000000000000 R11: 0000000000000000 R12: ffff9ac043d54700
> R13: ffff9ac043d54700 R14: 0000000000000001 R15: 0000000000000001
> FS: 00007f02e30ae000(0000) GS:ffff9afeb2440000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 000000012afca006 CR4: 0000000000770ee0
> PKRU: 55555554
> Call Trace:
> <TASK>
> ? __die+0x24/0x70
> ? page_fault_oops+0x82/0x150
> ? __iommu_queue_command_sync+0x80/0xc0
> ? exc_page_fault+0x69/0x150
> ? asm_exc_page_fault+0x26/0x30
> ? __iommu_attach_device+0xc/0xa0
> ? __iommu_attach_device+0x1c/0xa0
> __iommu_device_set_domain+0x42/0x80
> __iommu_group_set_domain_internal+0x5d/0x160
> iommu_setup_default_domain+0x318/0x400
> iommu_group_store_type+0xb1/0x200
> kernfs_fop_write_iter+0x12f/0x1c0
> vfs_write+0x2a2/0x3b0
> ksys_write+0x63/0xe0
> do_syscall_64+0x3f/0x90
> entry_SYSCALL_64_after_hwframe+0x6e/0xd8
> RIP: 0033:0x7f02e2f14a6f
>
> Reorganize the error flow so that the success branch and error branches
> are clearer.
>
> Cc:<stable@vger.kernel.org>
> Fixes: 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on ARM")
> Reported-by: Dheeraj Kumar Srivastava<dheerajkumar.srivastava@amd.com>
> Tested-by: Vasant Hegde<vasant.hegde@amd.com>
> Signed-off-by: Jason Gunthorpe<jgg@nvidia.com>
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Best regards,
baolu
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type
2023-06-26 15:13 [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type Jason Gunthorpe
2023-06-27 5:50 ` Tian, Kevin
2023-06-27 7:43 ` Baolu Lu
@ 2023-07-07 8:30 ` Joerg Roedel
2023-07-10 16:30 ` Jason Gunthorpe
2023-07-14 12:49 ` Joerg Roedel
3 siblings, 1 reply; 6+ messages in thread
From: Joerg Roedel @ 2023-07-07 8:30 UTC (permalink / raw)
To: Jason Gunthorpe
Cc: iommu, Joerg Roedel, Robin Murphy, Will Deacon, Lu Baolu,
Dheeraj Kumar Srivastava, Heiko Stuebner, Kevin Tian,
Niklas Schnelle, Vasant Hegde
On Mon, Jun 26, 2023 at 12:13:11PM -0300, Jason Gunthorpe wrote:
> The err_restore_domain flow was accidently inserted into the success path
> in commit 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on
> ARM"). It should only happen if iommu_create_device_direct_mappings()
> fails. This caused the domains the be wrongly changed and freed whenever
> the sysfs is used, resulting in an oops:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 0 P4D 0
> Oops: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 1 PID: 3417 Comm: avocado Not tainted 6.4.0-rc4-next-20230602 #3
> Hardware name: Dell Inc. PowerEdge R6515/07PXPY, BIOS 2.3.6 07/06/2021
> RIP: 0010:__iommu_attach_device+0xc/0xa0
> Code: c0 c3 cc cc cc cc 48 89 f0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 41 54 55 48 8b 47 08 <48> 8b 00 48 85 c0 74 74 48 89 f5 e8 64 12 49 00 41 89 c4 85 c0 74
> RSP: 0018:ffffabae0220bd48 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffff9ac04f70e410 RCX: 0000000000000001
> RDX: ffff9ac044db20c0 RSI: ffff9ac044fa50d0 RDI: ffff9ac04f70e410
> RBP: ffff9ac044fa50d0 R08: 1000000100209001 R09: 00000000000002dc
> R10: 0000000000000000 R11: 0000000000000000 R12: ffff9ac043d54700
> R13: ffff9ac043d54700 R14: 0000000000000001 R15: 0000000000000001
> FS: 00007f02e30ae000(0000) GS:ffff9afeb2440000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 000000012afca006 CR4: 0000000000770ee0
> PKRU: 55555554
> Call Trace:
> <TASK>
> ? __die+0x24/0x70
> ? page_fault_oops+0x82/0x150
> ? __iommu_queue_command_sync+0x80/0xc0
> ? exc_page_fault+0x69/0x150
> ? asm_exc_page_fault+0x26/0x30
> ? __iommu_attach_device+0xc/0xa0
> ? __iommu_attach_device+0x1c/0xa0
> __iommu_device_set_domain+0x42/0x80
> __iommu_group_set_domain_internal+0x5d/0x160
> iommu_setup_default_domain+0x318/0x400
> iommu_group_store_type+0xb1/0x200
> kernfs_fop_write_iter+0x12f/0x1c0
> vfs_write+0x2a2/0x3b0
> ksys_write+0x63/0xe0
> do_syscall_64+0x3f/0x90
> entry_SYSCALL_64_after_hwframe+0x6e/0xd8
> RIP: 0033:0x7f02e2f14a6f
>
> Reorganize the error flow so that the success branch and error branches
> are clearer.
>
> Cc: <stable@vger.kernel.org>
> Fixes: 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on ARM")
Why is this Cc stable? The causing patch is not in any released kernel.
Regards,
--
Jörg Rödel
jroedel@suse.de
SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type
2023-07-07 8:30 ` Joerg Roedel
@ 2023-07-10 16:30 ` Jason Gunthorpe
0 siblings, 0 replies; 6+ messages in thread
From: Jason Gunthorpe @ 2023-07-10 16:30 UTC (permalink / raw)
To: Joerg Roedel
Cc: iommu, Joerg Roedel, Robin Murphy, Will Deacon, Lu Baolu,
Dheeraj Kumar Srivastava, Heiko Stuebner, Kevin Tian,
Niklas Schnelle, Vasant Hegde
On Fri, Jul 07, 2023 at 10:30:45AM +0200, Joerg Roedel wrote:
> On Mon, Jun 26, 2023 at 12:13:11PM -0300, Jason Gunthorpe wrote:
> > The err_restore_domain flow was accidently inserted into the success path
> > in commit 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on
> > ARM"). It should only happen if iommu_create_device_direct_mappings()
> > fails. This caused the domains the be wrongly changed and freed whenever
> > the sysfs is used, resulting in an oops:
> >
> > BUG: kernel NULL pointer dereference, address: 0000000000000000
> > #PF: supervisor read access in kernel mode
> > #PF: error_code(0x0000) - not-present page
> > PGD 0 P4D 0
> > Oops: 0000 [#1] PREEMPT SMP NOPTI
> > CPU: 1 PID: 3417 Comm: avocado Not tainted 6.4.0-rc4-next-20230602 #3
> > Hardware name: Dell Inc. PowerEdge R6515/07PXPY, BIOS 2.3.6 07/06/2021
> > RIP: 0010:__iommu_attach_device+0xc/0xa0
> > Code: c0 c3 cc cc cc cc 48 89 f0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 41 54 55 48 8b 47 08 <48> 8b 00 48 85 c0 74 74 48 89 f5 e8 64 12 49 00 41 89 c4 85 c0 74
> > RSP: 0018:ffffabae0220bd48 EFLAGS: 00010246
> > RAX: 0000000000000000 RBX: ffff9ac04f70e410 RCX: 0000000000000001
> > RDX: ffff9ac044db20c0 RSI: ffff9ac044fa50d0 RDI: ffff9ac04f70e410
> > RBP: ffff9ac044fa50d0 R08: 1000000100209001 R09: 00000000000002dc
> > R10: 0000000000000000 R11: 0000000000000000 R12: ffff9ac043d54700
> > R13: ffff9ac043d54700 R14: 0000000000000001 R15: 0000000000000001
> > FS: 00007f02e30ae000(0000) GS:ffff9afeb2440000(0000) knlGS:0000000000000000
> > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > CR2: 0000000000000000 CR3: 000000012afca006 CR4: 0000000000770ee0
> > PKRU: 55555554
> > Call Trace:
> > <TASK>
> > ? __die+0x24/0x70
> > ? page_fault_oops+0x82/0x150
> > ? __iommu_queue_command_sync+0x80/0xc0
> > ? exc_page_fault+0x69/0x150
> > ? asm_exc_page_fault+0x26/0x30
> > ? __iommu_attach_device+0xc/0xa0
> > ? __iommu_attach_device+0x1c/0xa0
> > __iommu_device_set_domain+0x42/0x80
> > __iommu_group_set_domain_internal+0x5d/0x160
> > iommu_setup_default_domain+0x318/0x400
> > iommu_group_store_type+0xb1/0x200
> > kernfs_fop_write_iter+0x12f/0x1c0
> > vfs_write+0x2a2/0x3b0
> > ksys_write+0x63/0xe0
> > do_syscall_64+0x3f/0x90
> > entry_SYSCALL_64_after_hwframe+0x6e/0xd8
> > RIP: 0033:0x7f02e2f14a6f
> >
> > Reorganize the error flow so that the success branch and error branches
> > are clearer.
> >
> > Cc: <stable@vger.kernel.org>
> > Fixes: 1000dccd5d13 ("iommu: Allow IOMMU_RESV_DIRECT to work on ARM")
>
>
> Why is this Cc stable? The causing patch is not in any released kernel.
I don't keep track of when/where all the patches end up in stable. It
is now in -rc1 so it could be picked at any time. This is an important
bugfix so it should be backported if necessary.
If you know it is not in stable then please drop it when you merge it..
Otherwise it is harmless metadata, AFAIK.
Jason
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type
2023-06-26 15:13 [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type Jason Gunthorpe
` (2 preceding siblings ...)
2023-07-07 8:30 ` Joerg Roedel
@ 2023-07-14 12:49 ` Joerg Roedel
3 siblings, 0 replies; 6+ messages in thread
From: Joerg Roedel @ 2023-07-14 12:49 UTC (permalink / raw)
To: Jason Gunthorpe
Cc: iommu, Robin Murphy, Will Deacon, Lu Baolu,
Dheeraj Kumar Srivastava, Heiko Stuebner, Joerg Roedel,
Kevin Tian, Niklas Schnelle, Vasant Hegde
On Mon, Jun 26, 2023 at 12:13:11PM -0300, Jason Gunthorpe wrote:
> drivers/iommu/iommu.c | 31 ++++++++++++++++---------------
> 1 file changed, 16 insertions(+), 15 deletions(-)
Applied, thanks.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-07-14 12:49 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-26 15:13 [PATCH rc] iommu: Fix crash during syfs iommu_groups/N/type Jason Gunthorpe
2023-06-27 5:50 ` Tian, Kevin
2023-06-27 7:43 ` Baolu Lu
2023-07-07 8:30 ` Joerg Roedel
2023-07-10 16:30 ` Jason Gunthorpe
2023-07-14 12:49 ` Joerg Roedel
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.