public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: Felipe Ferreri Tonello <eu@felipetonello.com>,
	Felipe Balbi <balbi@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Cc: Robert Baldyga <r.baldyga@samsung.com>,
	Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
	Pawel Szewczyk <p.szewczyk@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 1/2] usb: gadget: f_midi: use flexible array member for gmidi_in_port elements
Date: Mon, 18 Jan 2016 17:02:29 +0100	[thread overview]
Message-ID: <xa1tbn8iq3je.fsf@mina86.com> (raw)
In-Reply-To: <569696CE.1000707@felipetonello.com>

> On 09/01/16 03:47, Michal Nazarewicz wrote:
>> @@ -55,7 +55,6 @@ static const char f_midi_longname[] = "MIDI Gadget";
>>   * USB <- IN endpoint  <- rawmidi
>>   */
>>  struct gmidi_in_port {
>> -	struct f_midi *midi;

On Wed, Jan 13 2016, Felipe Ferreri Tonello wrote:
> This change is unrelated. I sent a patch removing this pointer as well.

Has it been merged yet?  Which branch?  Could you point me to the patch?

>>  	int active;
>>  	uint8_t cable;
>>  	uint8_t state;
>> @@ -1115,26 +1112,16 @@ static struct usb_function *f_midi_alloc(struct usb_function_instance *fi)
>>  	}
>>  
>>  	/* allocate and initialize one new instance */
>> -	midi = kzalloc(sizeof(*midi), GFP_KERNEL);
>> +	midi = kzalloc(
>> +		sizeof(*midi) + opts->in_ports * sizeof(*midi->in_ports_array),
>> +		GFP_KERNEL);
>
> Is there a garantee that the compiler will always use in_ports_array at
> the end of the allocated block?

Yep, see <https://en.wikipedia.org/wiki/Flexible_array_member>.

>
>>  	if (!midi) {
>>  		mutex_unlock(&opts->lock);
>>  		return ERR_PTR(-ENOMEM);
>>  	}
>>  
>> -	for (i = 0; i < opts->in_ports; i++) {
>> -		struct gmidi_in_port *port = kzalloc(sizeof(*port), GFP_KERNEL);
>> -
>> -		if (!port) {
>> -			status = -ENOMEM;
>> -			mutex_unlock(&opts->lock);
>> -			goto setup_fail;
>> -		}
>> -
>> -		port->midi = midi;
>> -		port->active = 0;
>> -		port->cable = i;
>> -		midi->in_port[i] = port;
>> -	}
>> +	for (i = 0; i < opts->in_ports; i++)
>> +		midi->in_ports_array[i].cable = i;
>>  
>>  	/* set up ALSA midi devices */
>>  	midi->id = kstrdup(opts->id, GFP_KERNEL);

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  ミハウ “mina86” ナザレヴイツ  (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--

  parent reply	other threads:[~2016-01-18 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09  3:47 [PATCHv2 1/2] usb: gadget: f_midi: use flexible array member for gmidi_in_port elements Michal Nazarewicz
2016-01-09  3:47 ` [PATCH 2/2] usb: gadget: f_midi: missing unlock on error path Michal Nazarewicz
2016-01-13 18:29   ` Felipe Ferreri Tonello
2016-01-13 18:26 ` [PATCHv2 1/2] usb: gadget: f_midi: use flexible array member for gmidi_in_port elements Felipe Ferreri Tonello
2016-01-13 20:41   ` Dan Carpenter
2016-01-18 16:02   ` Michal Nazarewicz [this message]
2016-01-19  9:46     ` Felipe Ferreri Tonello

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=xa1tbn8iq3je.fsf@mina86.com \
    --to=mina86@mina86.com \
    --cc=andrzej.p@samsung.com \
    --cc=balbi@ti.com \
    --cc=dan.carpenter@oracle.com \
    --cc=eu@felipetonello.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.szewczyk@samsung.com \
    --cc=r.baldyga@samsung.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