Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: fireface: add field for the number of messages copied to user space
Date: Sat, 4 Feb 2023 09:55:27 +0900	[thread overview]
Message-ID: <Y92s/z+41aKOii/b@workstation> (raw)
In-Reply-To: <87fsbmn2gf.wl-tiwai@suse.de>

Hi,

On Fri, Feb 03, 2023 at 05:22:40PM +0100, Takashi Iwai wrote:
> On Thu, 02 Feb 2023 14:37:08 +0100,
> Takashi Sakamoto wrote:
> > 
> > Current structure includes no field to express the number of messages
> > copied to user space, thus user space application needs to information
> > out of the structure to parse the content of structure.
> > 
> > This commit adds a field to express the number of messages copied to user
> > space since It is more preferable to use self-contained structure.
> > 
> > Kees Cook proposed an idea of annotation for bound of flexible arrays
> > in his future improvement for flexible-length array in kernel. The
> > additional field for message count is suitable to the idea as well.
> > 
> > Reference: https://people.kernel.org/kees/bounded-flexible-arrays-in-c
> > Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> 
> Wouldn't changing this break the existing application that talks with
> the older ABI?  Just to be sure...

You may well have the concern, indeed.

The structure is not exposed to user space yet, since it was added by a
commit ab811cfffa9 ("ALSA: fireface: update UAPI for data of knob
control"). It just exists in your (and mine) tree at present.


Thanks

Takashi Sakamoto

  reply	other threads:[~2023-02-04  0:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 13:37 [PATCH] ALSA: fireface: add field for the number of messages copied to user space Takashi Sakamoto
2023-02-03 16:22 ` Takashi Iwai
2023-02-04  0:55   ` Takashi Sakamoto [this message]
2023-02-04  8:36     ` Takashi Iwai

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=Y92s/z+41aKOii/b@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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