From: Kaushlendra Kumar <kaushlendra.kumar@intel.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org,
Kaushlendra Kumar <kaushlendra.kumar@intel.com>
Subject: [PATCH] PCI/VGA: release vga_user_lock before vga_put()
Date: Wed, 1 Oct 2025 11:28:13 +0530 [thread overview]
Message-ID: <20251001055813.264300-1-kaushlendra.kumar@intel.com> (raw)
Release vga_user_lock immediately after list_del() and before calling
vga_put(). The vga_put() function acquires vga_lock internally, and
holding vga_user_lock while calling vga_put(). The VGA resource
operations and loop iteration don't require lock protection, only
the list removal needs lock protection.
This ensures consistent lock ordering and eliminates the deadlock risk
during VGA resource cleanup operations.
Signed-off-by: Kaushlendra Kumar <kaushlendra.kumar@intel.com>
---
drivers/pci/vgaarb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/vgaarb.c b/drivers/pci/vgaarb.c
index 78748e8d2dba..e86fe7fa3d6f 100644
--- a/drivers/pci/vgaarb.c
+++ b/drivers/pci/vgaarb.c
@@ -1445,6 +1445,7 @@ static int vga_arb_release(struct inode *inode, struct file *file)
spin_lock_irqsave(&vga_user_lock, flags);
list_del(&priv->list);
+ spin_unlock_irqrestore(&vga_user_lock, flags);
for (i = 0; i < MAX_USER_CARDS; i++) {
uc = &priv->cards[i];
if (uc->pdev == NULL)
@@ -1456,7 +1457,6 @@ static int vga_arb_release(struct inode *inode, struct file *file)
while (uc->mem_cnt--)
vga_put(uc->pdev, VGA_RSRC_LEGACY_MEM);
}
- spin_unlock_irqrestore(&vga_user_lock, flags);
kfree(priv);
--
2.34.1
reply other threads:[~2025-10-01 6:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251001055813.264300-1-kaushlendra.kumar@intel.com \
--to=kaushlendra.kumar@intel.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox