[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231017164946.623abd0d@xps-13>
Date: Tue, 17 Oct 2023 16:49:46 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Frank Li <Frank.li@....com>
Cc: conor.culhane@...vaco.com, alexandre.belloni@...tlin.com,
joe@...ches.com, linux-i3c@...ts.infradead.org,
linux-kernel@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH 1/6] i3c: master: svc: fix race condition in ibi work
thread
Hi Frank,
Frank.li@....com wrote on Tue, 17 Oct 2023 10:37:57 -0400:
> On Tue, Oct 17, 2023 at 04:16:58PM +0200, Miquel Raynal wrote:
> > Hi Frank,
> >
> > Frank.Li@....com wrote on Mon, 16 Oct 2023 11:32:27 -0400:
> >
> > > The ibi work thread operates asynchronously with other transfers, such as
> > > svc_i3c_master_priv_xfers(). Introduces mutex protection to ensure the
> >
> > Introduce
> >
> > > completion of the entire i3c/i2c transaction.
> >
> > Did you experience faulty conditions or was it reported thanks to
> > static analysis?
>
> Yes, I met. But it needs my slave part patches, which will be ready sent
> out review soon.
I believe several of the "fixes" in this series are related to newer
uses (typically your i3c slave support) which were not in the scope of
the original submission. As these new features are not supposed to be
backported in stable kernels and because these are new corner cases,you
may drop the CC:/Fixes tags to avoid useless backports.
Some of them however are real fixes for situations we may happen with
the current level of support, please keep the tags in these, and move
them all to the beginning of your series.
Thanks,
Miquèl
Powered by blists - more mailing lists