From: Hardik Phalet <hardik.phalet@pm.me>
To: Ferenc Bakonyi <fero@drama.obuda.kando.hu>, Helge Deller <deller@gmx.de>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Brigham Campbell <me@brighamcampbell.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-nvidia@lists.surfsouth.com, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Hardik Phalet <hardik.phalet@pm.me>
Subject: [PATCH] fbdev/hga: Request memory region before ioremap
Date: Tue, 10 Mar 2026 06:41:43 +0000 [thread overview]
Message-ID: <20260310064124.602848-1-hardik.phalet@pm.me> (raw)
The driver calls ioremap() on the HGA video memory at 0xb0000 without
first reserving the physical address range via request_mem_region().
This leaves the kernel resource tree incomplete and can cause silent
conflicts with other drivers claiming the same range.
Add a request_mem_region() call before ioremap() in hga_card_detect()
and release the region in all error paths and in hgafb_remove().
Signed-off-by: Hardik Phalet <hardik.phalet@pm.me>
---
drivers/video/fbdev/hgafb.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/hgafb.c b/drivers/video/fbdev/hgafb.c
index 14418aa3791a..ceca6cc2c928 100644
--- a/drivers/video/fbdev/hgafb.c
+++ b/drivers/video/fbdev/hgafb.c
@@ -284,9 +284,16 @@ static int hga_card_detect(void)
hga_vram_len = 0x08000;
+ if (!request_mem_region(0xb0000, hga_vram_len, "hgafb")) {
+ pr_err("hgafb: cannot reserve video memory at 0xb0000\n");
+ return -EBUSY;
+ }
+
hga_vram = ioremap(0xb0000, hga_vram_len);
- if (!hga_vram)
+ if (!hga_vram) {
+ release_mem_region(0xb0000, hga_vram_len);
return -ENOMEM;
+ }
if (request_region(0x3b0, 12, "hgafb"))
release_io_ports = 1;
@@ -348,6 +355,7 @@ static int hga_card_detect(void)
}
return 0;
error:
+ release_mem_region(0xb0000, hga_vram_len);
if (release_io_ports)
release_region(0x3b0, 12);
if (release_io_port)
@@ -619,6 +627,7 @@ static void hgafb_remove(struct platform_device *pdev)
}
iounmap(hga_vram);
+ release_mem_region(0xb0000, hga_vram_len);
if (release_io_ports)
release_region(0x3b0, 12);
--
2.53.0
next reply other threads:[~2026-03-10 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 6:41 Hardik Phalet [this message]
2026-03-10 10:03 ` [PATCH] fbdev/hga: Request memory region before ioremap Thomas Zimmermann
2026-03-11 3:36 ` Claude review: " Claude Code Review Bot
2026-03-11 3:36 ` Claude Code Review Bot
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=20260310064124.602848-1-hardik.phalet@pm.me \
--to=hardik.phalet@pm.me \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=fero@drama.obuda.kando.hu \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvidia@lists.surfsouth.com \
--cc=me@brighamcampbell.com \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
/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