From: Johan Hovold <johan@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Johan Hovold <johan@kernel.org>,
Octavian Purdila <octavian.purdila@intel.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mfd: viperboard: allocate I/O buffer separately
Date: Wed, 24 Sep 2014 14:26:58 +0200 [thread overview]
Message-ID: <20140924122658.GD17019@localhost> (raw)
In-Reply-To: <20140924120002.GA32069@lee--X1>
On Wed, Sep 24, 2014 at 01:00:02PM +0100, Lee Jones wrote:
> On Wed, 24 Sep 2014, Johan Hovold wrote:
>
> > On Wed, Sep 24, 2014 at 11:12:06AM +0100, Lee Jones wrote:
> > > On Mon, 22 Sep 2014, Octavian Purdila wrote:
> > >
> > > > Currently the I/O buffer is allocated part of the device status
> > > > structure, potentially sharing the same cache line with other members
> > > > in this structure.
> > > >
> > > > Allocate the buffer separately, to avoid the I/O operations corrupting
> > > > the device status structure due to cache line sharing.
> > > >
> > > > Compiled tested only as I don't have access to hardware.
> > > >
> > > > Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
> > > > ---
> > > > drivers/mfd/viperboard.c | 8 ++++++++
> > > > include/linux/mfd/viperboard.h | 2 +-
> > > > 2 files changed, 9 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/mfd/viperboard.c b/drivers/mfd/viperboard.c
> > > > index e00f534..5f62f4e 100644
> > > > --- a/drivers/mfd/viperboard.c
> > > > +++ b/drivers/mfd/viperboard.c
> > > > @@ -64,6 +64,12 @@ static int vprbrd_probe(struct usb_interface *interface,
> > > > return -ENOMEM;
> > > > }
> > > >
> > > > + vb->buf = kzalloc(sizeof(struct vprbrd_i2c_write_msg), GFP_KERNEL);
> > >
> > > Can you obtain the 'struct device' first then use managed resources
> > > (devm_*)?
> >
> > I think any devres conversion should be done in a follow-up patch and
> > not be included in the fix (e.g. in order to facilitate backporting). We
> > also don't want to mix allocation schemes.
>
> I agree, but equally I'm not keen on accepting this patch as I believe
> it could be done better.
>
> Please submit two patches, one converting to shared resources and this
> being the subsequent one, fixed up to do the right thing.
A buffer-corruption fix is a candidate for stable, whereas a devres
conversion (clean up) is not. Hence the former should not depend on the
latter.
Johan
next prev parent reply other threads:[~2014-09-24 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 19:39 [PATCH v2 0/2] mfd: viperboard: cleanups and fix for cache line sharing Octavian Purdila
2014-09-22 19:39 ` [PATCH v2 1/2] mfd: viperboard: allocate I/O buffer separately Octavian Purdila
2014-09-23 7:35 ` Johan Hovold
2014-09-23 7:38 ` Johan Hovold
2014-09-23 7:47 ` Johan Hovold
2014-09-24 10:12 ` Lee Jones
2014-09-24 10:28 ` Johan Hovold
2014-09-24 12:00 ` Lee Jones
2014-09-24 12:26 ` Johan Hovold [this message]
2014-09-24 12:34 ` Octavian Purdila
2014-09-24 12:34 ` Johan Hovold
2014-09-22 19:39 ` [PATCH v2 2/2] mfd: viperboard: remove redundant OOM message and NULL pointer check Octavian Purdila
2014-09-24 10:13 ` Lee Jones
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=20140924122658.GD17019@localhost \
--to=johan@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=octavian.purdila@intel.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