Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <mlimonci@amd.com>
Cc: Martin.Leung@amd.com, Hanghong.Ma@amd.com,
	alexander.deucher@amd.com, daniel.wheeler@amd.com,
	mario.limonciello@amd.com, qingqing.zhuo@amd.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/amd/display: fix double memory allocation" failed to apply to 6.3-stable tree
Date: Sat, 13 May 2023 21:59:33 +0900	[thread overview]
Message-ID: <2023051308-step-handful-f179@gregkh> (raw)
In-Reply-To: <cca06775-c451-0247-9262-71c67a215a60@amd.com>

On Sat, May 13, 2023 at 07:28:20AM -0500, Mario Limonciello wrote:
> On 5/13/23 02:20, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 6.3-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> > To reproduce the conflict and resubmit, you may use the following commands:
> > 
> > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.3.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x f5442b35e69e42015ef3082008c0d85cdcc0ca05
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023051306-elves-dividers-01e7@gregkh' --subject-prefix 'PATCH 6.3.y' HEAD^..
> > 
> > Possible dependencies:
> > 
> > f5442b35e69e ("drm/amd/display: fix double memory allocation")
> > b5006f873b99 ("drm/amd/display: initialize link_srv in virtual env")
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > ------------------ original commit in Linus's tree ------------------
> > 
> >  From f5442b35e69e42015ef3082008c0d85cdcc0ca05 Mon Sep 17 00:00:00 2001
> > From: Martin Leung <Martin.Leung@amd.com>
> > Date: Tue, 14 Mar 2023 09:27:20 -0400
> > Subject: [PATCH] drm/amd/display: fix double memory allocation
> > 
> > [Why & How]
> > when trying to fix a nullptr dereference on VMs,
> > accidentally doubly allocated memory for the non VM
> > case. removed the extra link_srv creation since
> > dc_construct_ctx is called in both VM and non VM cases
> > Also added a proper fail check for if kzalloc fails
> > 
> > Cc: stable@vger.kernel.org
> > Cc: Mario Limonciello <mario.limonciello@amd.com>
> > Reviewed-by: Leo Ma <Hanghong.Ma@amd.com>
> > Acked-by: Qingqing Zhuo <qingqing.zhuo@amd.com>
> > Signed-off-by: Martin Leung <Martin.Leung@amd.com>
> > Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > 
> > diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c
> > index 40f2e174c524..52564b93f7eb 100644
> > --- a/drivers/gpu/drm/amd/display/dc/core/dc.c
> > +++ b/drivers/gpu/drm/amd/display/dc/core/dc.c
> > @@ -887,7 +887,10 @@ static bool dc_construct_ctx(struct dc *dc,
> >   	}
> >   	dc->ctx = dc_ctx;
> > +
> >   	dc->link_srv = link_create_link_service();
> > +	if (!dc->link_srv)
> > +		return false;
> >   	return true;
> >   }
> > @@ -986,8 +989,6 @@ static bool dc_construct(struct dc *dc,
> >   		goto fail;
> >   	}
> > -	dc->link_srv = link_create_link_service();
> > -
> >   	dc->res_pool = dc_create_resource_pool(dc, init_params, dc_ctx->dce_version);
> >   	if (!dc->res_pool)
> >   		goto fail;
> > 
> 
> FYI -
> This particular commit didn't need to come back to any stable channels as
> the commit it fixed
> b5006f873b99 ("drm/amd/display: initialize link_srv in virtual env")
> is only present in 6.4.

Any reason why a "Fixes:" tag wasn't added here?  That would have made
it much easier to figure this all out :)

thanks,

greg k-h

      reply	other threads:[~2023-05-13 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13  7:20 FAILED: patch "[PATCH] drm/amd/display: fix double memory allocation" failed to apply to 6.3-stable tree gregkh
2023-05-13 12:28 ` Mario Limonciello
2023-05-13 12:59   ` Greg KH [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=2023051308-step-handful-f179@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Hanghong.Ma@amd.com \
    --cc=Martin.Leung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=daniel.wheeler@amd.com \
    --cc=mario.limonciello@amd.com \
    --cc=mlimonci@amd.com \
    --cc=qingqing.zhuo@amd.com \
    --cc=stable@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