public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	tiwai@suse.de, stable@vger.kernel.org,
	Edmund Raile <edmund.raile@proton.me>
Subject: Re: [PATCH] ALSA: firewire-lib: fix wrong value as length of header for CIP_NO_HEADER case
Date: Thu, 25 Jul 2024 18:11:38 +0200	[thread overview]
Message-ID: <877cd9ih8l.wl-tiwai@suse.de> (raw)
In-Reply-To: <94600ca4-47ce-4993-b6ce-dabb93ef01dc@embeddedor.com>

On Thu, 25 Jul 2024 18:08:21 +0200,
Gustavo A. R. Silva wrote:
> 
> 
> 
> On 25/07/24 09:56, Takashi Sakamoto wrote:
> > In a commit 1d717123bb1a ("ALSA: firewire-lib: Avoid
> > -Wflex-array-member-not-at-end warning"), DEFINE_FLEX() macro was used to
> > handle variable length of array for header field in struct fw_iso_packet
> > structure. The usage of macro has a side effect that the designated
> > initializer assigns the count of array to the given field. Therefore
> > CIP_HEADER_QUADLETS (=2) is assigned to struct fw_iso_packet.header,
> > while the original designated initializer assigns zero to all fields.
> > 
> > With CIP_NO_HEADER flag, the change causes invalid length of header in
> > isochronous packet for 1394 OHCI IT context. This bug affects all of
> > devices supported by ALSA fireface driver; RME Fireface 400, 800, UCX, UFX,
> > and 802.
> > 
> > This commit fixes the bug by replacing it with the alternative version of
> > macro which corresponds no initializer.
> 
> This change is incomplete. The patch I mention here[1] should also be applied.

Yes, but this can be fixed by another patch, right?
At least the regression introduced by the given commit can be fixed by
that.  The other fix can go through Sakamoto-san's firewire tree
individually.


thanks,

Takashi

> BTW, there is one more line that should probably be changed in `struct fw_iso_packet`
> to avoid further confusions:
> 
> -       u16 payload_length;     /* Length of indirect payload           */
> +       u16 payload_length;     /* Size of indirect payload             */
> 
> Thanks
> --
> Gustavo
> 
> [1] https://lore.kernel.org/linux-sound/dabb394e-6c85-45a0-bc06-7a45262a9a8c@embeddedor.com/T/#m0b9b0e7dd4561dc58422cf15df2dbd2ddb44b54b
> 
> > 
> > Cc: <stable@vger.kernel.org>
> > Fixes: 1d717123bb1a ("ALSA: firewire-lib: Avoid -Wflex-array-member-not-at-end warning")
> > Reported-by: Edmund Raile <edmund.raile@proton.me>
> > Closes: https://lore.kernel.org/r/rrufondjeynlkx2lniot26ablsltnynfaq2gnqvbiso7ds32il@qk4r6xps7jh2/
> > Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> > ---
> >   sound/firewire/amdtp-stream.c | 3 +--
> >   1 file changed, 1 insertion(+), 2 deletions(-)
> > 
> > diff --git a/sound/firewire/amdtp-stream.c b/sound/firewire/amdtp-stream.c
> > index d35d0a420ee0..1a163bbcabd7 100644
> > --- a/sound/firewire/amdtp-stream.c
> > +++ b/sound/firewire/amdtp-stream.c
> > @@ -1180,8 +1180,7 @@ static void process_rx_packets(struct fw_iso_context *context, u32 tstamp, size_
> >   		(void)fw_card_read_cycle_time(fw_parent_device(s->unit)->card, &curr_cycle_time);
> >     	for (i = 0; i < packets; ++i) {
> > -		DEFINE_FLEX(struct fw_iso_packet, template, header,
> > -			    header_length, CIP_HEADER_QUADLETS);
> > +		DEFINE_RAW_FLEX(struct fw_iso_packet, template, header, CIP_HEADER_QUADLETS);
> >   		bool sched_irq = false;
> >     		build_it_pkt_header(s, desc->cycle, template,
> > pkt_header_length,

  reply	other threads:[~2024-07-25 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 15:56 [PATCH] ALSA: firewire-lib: fix wrong value as length of header for CIP_NO_HEADER case Takashi Sakamoto
2024-07-25 16:07 ` Takashi Iwai
2024-07-25 16:08 ` Gustavo A. R. Silva
2024-07-25 16:11   ` Takashi Iwai [this message]
2024-07-25 16:16     ` Gustavo A. R. Silva
2024-07-25 16:25       ` Takashi Sakamoto
2024-07-25 17:52         ` Takashi Iwai
2024-07-26  0:20           ` Takashi Sakamoto
2024-07-27  1:35 ` Takashi Sakamoto

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=877cd9ih8l.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=edmund.raile@proton.me \
    --cc=gustavo@embeddedor.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=stable@vger.kernel.org \
    /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