From: Daniel Vetter <daniel@ffwll.ch>
To: Ondrej Zary <linux@zary.sk>
Cc: Helge Deller <deller@gmx.de>,
jiapeng.chong@linux.alibaba.com, linux-fbdev@vger.kernel.org,
javierm@redhat.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, tzimmermann@suse.de,
Zhang Shurong <zhang_shurong@foxmail.com>
Subject: Re: [PATCH] video: fbdev: arkfb: fix possible object reference leak
Date: Tue, 10 Oct 2023 13:45:57 +0200 [thread overview]
Message-ID: <ZSU5dZJqd8CIFzM6@phenom.ffwll.local> (raw)
In-Reply-To: <202310061634.02110.linux@zary.sk>
On Fri, Oct 06, 2023 at 04:34:01PM +0200, Ondrej Zary wrote:
> On Friday 06 October 2023, Helge Deller wrote:
> > On 10/5/23 09:01, Zhang Shurong wrote:
> > > Add missing pci_disable_device() in error path in ark_pci_probe().
> >
> > Do you have this hardware and tested your patch?
> > I'm sure there is a reason, why "pci_disable_device()" was commented
> > out in the original submission in commit 681e14730c73c...
>
> pci_disable_device() call is disabled in many fbdev drivers because
> calling it might prevent display from working.
Yeah I've recently hit some _really_ interesting regression report where
essentially fbdev driver and vgacon where managing the hardware
collaboratively. There's enormous amounts of "this shouldn't work like
that, but it is how it does" going on in old fbdev drivers, and what you
brought up is also what I immediately thought of.
This patch feels way too risky to me that we should apply it ...
-Sima
>
> >
> > Additionally I'm wondering why your patch doesn't show up in
> > the fbdev patchwork, although you added linux-fbdev mailing list.
> > Probably a vger issue.
> >
> > Helge
> >
> >
> > > Signed-off-by: Zhang Shurong <zhang_shurong@foxmail.com>
> > > ---
> > > drivers/video/fbdev/arkfb.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/video/fbdev/arkfb.c b/drivers/video/fbdev/arkfb.c
> > > index 60a96fdb5dd8..6c4e5065646f 100644
> > > --- a/drivers/video/fbdev/arkfb.c
> > > +++ b/drivers/video/fbdev/arkfb.c
> > > @@ -1064,7 +1064,7 @@ static int ark_pci_probe(struct pci_dev *dev, const struct pci_device_id *id)
> > > err_dac:
> > > pci_release_regions(dev);
> > > err_request_regions:
> > > -/* pci_disable_device(dev); */
> > > + pci_disable_device(dev);
> > > err_enable_device:
> > > framebuffer_release(info);
> > > return rc;
> > > @@ -1085,7 +1085,7 @@ static void ark_pci_remove(struct pci_dev *dev)
> > >
> > > pci_iounmap(dev, info->screen_base);
> > > pci_release_regions(dev);
> > > -/* pci_disable_device(dev); */
> > > + pci_disable_device(dev);
> > >
> > > framebuffer_release(info);
> > > }
> >
> >
>
>
>
> --
> Ondrej Zary
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2023-10-10 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_55C1A344A101B55762ECA6A6366D0B0F8C05@qq.com>
2023-10-06 8:09 ` [PATCH] video: fbdev: arkfb: fix possible object reference leak Helge Deller
2023-10-06 11:19 ` Zhang Shurong
2023-10-06 14:34 ` Ondrej Zary
2023-10-10 11:45 ` Daniel Vetter [this message]
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=ZSU5dZJqd8CIFzM6@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zary.sk \
--cc=tzimmermann@suse.de \
--cc=zhang_shurong@foxmail.com \
/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;
as well as URLs for NNTP newsgroup(s).