[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHUa44F3ic_Fu-pLsZ2sZeC69TSLwKZjegdkCB-xpm=Zm6J4PA@mail.gmail.com>
Date: Tue, 5 Apr 2022 09:02:26 +0200
From: Jens Wiklander <jens.wiklander@...aro.org>
To: Dongliang Mu <mudongliangabcd@...il.com>
Cc: Dongliang Mu <dzm91@...t.edu.cn>,
Sumit Garg <sumit.garg@...aro.org>,
op-tee@...ts.trustedfirmware.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tee: optee: add missing mutext_destroy in optee_ffa_probe
On Fri, Apr 1, 2022 at 4:00 AM Dongliang Mu <mudongliangabcd@...il.com> wrote:
>
> On Thu, Mar 24, 2022 at 5:33 PM Dongliang Mu <mudongliangabcd@...il.com> wrote:
> >
> > On Thu, Mar 24, 2022 at 4:29 PM Jens Wiklander
> > <jens.wiklander@...aro.org> wrote:
> > >
> > > On Wed, Mar 16, 2022 at 2:51 PM Dongliang Mu <dzm91@...t.edu.cn> wrote:
> > > >
> > > > From: Dongliang Mu <mudongliangabcd@...il.com>
> > > >
> > > > The error handling code of optee_ffa_probe misses the mutex_destroy of
> > > > ffa.mutex when mutext_init succeeds.
> > > >
> > > > Fix this by adding mutex_destory of ffa.mutex at the error handling part
> > > >
> > > > Fixes: aceeafefff73 ("optee: use driver internal tee_context for some rpc")
> > >
> > > I believe this should be
> > > Fixes: 4615e5a34b95 ("optee: add FF-A support")
> > > don't you agree?
> >
> > Hi Jen,
> >
> > This commit 4615e5a34b95 is more suitable since mutex_init is introduced here.
> >
> > Why did I label the commit aceeafefff73?
> >
> > Because this commit tried to fix the issue, but only added one
> > mutex_destroy for &optee->call_queue.mutex, misses &optee->ffa.mutex.
> >
>
> ping?
I'm picking up this.
Thanks,
Jens
Powered by blists - more mailing lists