All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sa, Nuno" <Nuno.Sa@analog.com>
To: Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Eugen Hristev <eugen.hristev@microchip.com>,
	Andreas Klinger <ak@it-klinger.d>,
	Song Qiang <songqiang1304521@gmail.com>,
	Mathieu Othacehe <m.othacehe@gmail.com>,
	Parthiban Nallathambi <pn@denx.de>
Subject: RE: [PATCH RESEND 0/8] IIO: Alignment fixes part 3 - __aligned(8) used to ensure alignment
Date: Mon, 14 Jun 2021 08:03:20 +0000	[thread overview]
Message-ID: <PH0PR03MB6366479D135F6D96D3FD4F1C99319@PH0PR03MB6366.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20210613152301.571002-1-jic23@kernel.org>

Hi Jonathan,

> From: Jonathan Cameron <jic23@kernel.org>
> Sent: Sunday, June 13, 2021 5:23 PM
> To: linux-iio@vger.kernel.org
> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>; Eugen
> Hristev <eugen.hristev@microchip.com>; Andreas Klinger <ak@it-
> klinger.d>; Song Qiang <songqiang1304521@gmail.com>; Mathieu
> Othacehe <m.othacehe@gmail.com>; Parthiban Nallathambi
> <pn@denx.de>
> Subject: [PATCH RESEND 0/8] IIO: Alignment fixes part 3 - __aligned(8)
> used to ensure alignment
> 
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> 
> Resent as none of these have had any comments since being sent out
> over
> a month ago.  Note these are very straight forward, but I've messed up
> such things in the past so really appreciate it if someone takes the time
> to do a quick sanity check.
> 
> I have picked up those patches that did get review in first posting and
> dropped them from this posting.
> 
> Cover letter from first posting.
> 
> I finally got around to do a manual audit of all the calls to
> iio_push_to_buffers_with_timestamp() which has the somewhat odd
> requirements
> of:
> 1. 8 byte alignment of the provided buffer.
> 2. space for an 8 byte naturally aligned timestamp to be inserted at the
>    end.
> 
> Unfortunately there were rather a lot of these left, but time to bite
> the bullet
> and clean them up.
> 
> As discussed previous in
> https://urldefense.com/v3/__https://lore.kernel.org/linux-
> iio/20200920112742.170751-1-
> jic23@kernel.org/__;!!A3Ni8CS0y2Y!uCn6NSpGUvHYdcFazn7flxxjh8RA
> RqPCumitrRDDgGAjXF7crgi911KY2v_iyw$
> it is not easy to fix the alignment issue without requiring a bounce
> buffer
> (see part 4 of the alignment fixes for a proposal for that where it is
> absolutely necessary).
> 
> Part 3 contains the cases where the struct approach in part 2 did not
> seem
> appropriate.  Normally there are two possible reasons for this.
> 1.  Would have required an additional memset operation to avoid any
>     possibility of leaking kernel data.
> 2.  The location of the timestamp may depend on the channels
> enabled.
>     This normally happens when the max sizeof channels is greater than
>     8 bytes.
> 
> Once all cases are fixes, I'll take a look at hardening against any
> accidental reintroductions. Note that on many platforms and usecases
> the
> bug in question will never occur.
> 
> Cc: Eugen Hristev <eugen.hristev@microchip.com>
> Cc: Andreas Klinger <ak@it-klinger.d>
> Cc: Song Qiang <songqiang1304521@gmail.com>
> Cc: Mathieu Othacehe <m.othacehe@gmail.com>
> Cc: Parthiban Nallathambi <pn@denx.de>
> 
> Jonathan Cameron (8):
>   iio: adc: at91-sama5d2: Fix buffer alignment in
>     iio_push_to_buffers_with_timestamp()
>   iio: adc: hx711: Fix buffer alignment in
>     iio_push_to_buffers_with_timestamp()
>   iio: adc: mxs-lradc: Fix buffer alignment in
>     iio_push_to_buffers_with_timestamp()
>   iio: adc: ti-ads8688: Fix alignment of buffer in
>     iio_push_to_buffers_with_timestamp()
>   iio: magn: rm3100: Fix alignment of buffer in
>     iio_push_to_buffers_with_timestamp()
>   iio: light: vcnl4000: Fix buffer alignment in
>     iio_push_to_buffers_with_timestamp()
>   iio: light: vcnl4035: Fix buffer alignment in
>     iio_push_to_buffers_with_timestamp()
>   iio: prox: isl29501: Fix buffer alignment in
>     iio_push_to_buffers_with_timestamp()
> 
>  drivers/iio/adc/at91-sama5d2_adc.c     | 3 ++-
>  drivers/iio/adc/hx711.c                | 4 ++--
>  drivers/iio/adc/mxs-lradc-adc.c        | 3 ++-
>  drivers/iio/adc/ti-ads8688.c           | 3 ++-
>  drivers/iio/light/vcnl4000.c           | 2 +-
>  drivers/iio/light/vcnl4035.c           | 3 ++-
>  drivers/iio/magnetometer/rm3100-core.c | 3 ++-
>  drivers/iio/proximity/isl29501.c       | 2 +-
>  8 files changed, 14 insertions(+), 9 deletions(-)
> 
> --
> 2.32.0

LGTM. For the whole series:

Reviewed-by: Nuno Sá <nuno.sa@analog.com>

- Nuno Sá

  parent reply	other threads:[~2021-06-14  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 15:22 [PATCH RESEND 0/8] IIO: Alignment fixes part 3 - __aligned(8) used to ensure alignment Jonathan Cameron
2021-06-13 15:22 ` [PATCH RESEND 1/8] iio: adc: at91-sama5d2: Fix buffer alignment in iio_push_to_buffers_with_timestamp() Jonathan Cameron
2021-06-13 15:22 ` [PATCH RESEND 2/8] iio: adc: hx711: " Jonathan Cameron
2021-06-13 15:22 ` [PATCH RESEND 3/8] iio: adc: mxs-lradc: " Jonathan Cameron
2021-06-13 15:22 ` [PATCH RESEND 4/8] iio: adc: ti-ads8688: Fix alignment of buffer " Jonathan Cameron
2021-06-13 15:22 ` [PATCH RESEND 5/8] iio: magn: rm3100: " Jonathan Cameron
2021-06-13 15:22 ` [PATCH RESEND 6/8] iio: light: vcnl4000: Fix buffer alignment " Jonathan Cameron
2021-06-13 15:23 ` [PATCH RESEND 7/8] iio: light: vcnl4035: " Jonathan Cameron
2021-06-13 15:23 ` [PATCH RESEND 8/8] iio: prox: isl29501: " Jonathan Cameron
2021-06-14  8:03 ` Sa, Nuno [this message]
2021-06-14 10:43   ` [PATCH RESEND 0/8] IIO: Alignment fixes part 3 - __aligned(8) used to ensure alignment Jonathan Cameron

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=PH0PR03MB6366479D135F6D96D3FD4F1C99319@PH0PR03MB6366.namprd03.prod.outlook.com \
    --to=nuno.sa@analog.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=ak@it-klinger.d \
    --cc=eugen.hristev@microchip.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=m.othacehe@gmail.com \
    --cc=pn@denx.de \
    --cc=songqiang1304521@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.