[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+ASDXMkWha7Lrf8TrDhyF2fXonPjqLKvyKFzVQthxDQUOp=kQ@mail.gmail.com>
Date: Wed, 3 Apr 2019 11:39:38 -0700
From: Brian Norris <briannorris@...omium.org>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: Doug Anderson <dianders@...omium.org>,
Benson Leung <bleung@...omium.org>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Alexandru M Stan <amstan@...omium.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Simon Glass <sjg@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Mark Brown <broonie@...nel.org>,
Ryan Case <ryandcase@...omium.org>,
Randall Spangler <rspangler@...omium.org>,
Heiko Stuebner <heiko@...ech.de>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] platform/chrome: cros_ec_spi: Transfer messages at
high priority
On Wed, Apr 3, 2019 at 11:30 AM Matthias Kaehlcke <mka@...omium.org> wrote:
> The worker is owned by this driver and supposedly we know what we are
> doing. Changing a member in the struct after calling complete() would
> likely be a bug anyway (though not necessarily a fatal one).
The work_struct is owned by the driver, but the *worker* is not. If we
haven't ensured the worker is totally done with the work_struct, then
we should not be freeing the struct. (i.e., we should not return from
the context where it was stack-allocated.)
Anyway, I think we've all agreed that this should be changed,
Brian
Powered by blists - more mailing lists