From: Krzysztof Opasiak <k.opasiak@samsung.com>
To: Michal Nazarewicz <mina86@mina86.com>, balbi@ti.com
Cc: stable@vger.kernel.org, david.fisher1@synopsys.com,
gregkh@linuxfoundation.org, andrzej.p@samsung.com,
m.szyprowski@samsung.com, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 4/5] usb: gadget: mass_storage: Use static array for luns
Date: Mon, 20 Jul 2015 16:09:37 +0200 [thread overview]
Message-ID: <55AD0121.4070107@samsung.com> (raw)
In-Reply-To: <xa1ty4ibge8h.fsf@mina86.com>
On 07/20/2015 03:17 PM, Michal Nazarewicz wrote:
>> On 07/08/2015 04:00 PM, Michal Nazarewicz wrote:
>>> On Tue, Jul 07 2015, Krzysztof Opasiak wrote:
>>>> This patch replace dynamicly allocated luns array with static one.
>>>> This simplifies the code of mass storage function and modules.
>>>>
>>>> It also fix issue with reporting wrong number of LUNs in GET_MAX_LUN
>>>> request. According to MS spec we should return the max index of valid
>>>> LUN, not the number of luns - 1.
>>>
>>> This is no longer true, is it? Why my fix this bug has been solved, no?
>>> As such, this should not go to stable. Or am I missing something?
>
> On Mon, Jul 20 2015, Krzysztof Opasiak wrote:
>> Unfortunately it's still true. Your fix solved this bug partially. Now
>> we report nluns - 1 instead of FSG_LUN_MAX but in case of not contiguous
>> luns it is not enough.
>>
>> Let's consider mass storage function with luns 0 1 3 5. nluns == 4 so in
>> GET_MAX_LUN we will return 3 (nluns - 1).
>
> I don’t believe that’s accurate. See loop in my patch:
>
> + if (!opts->refcnt) {
> + for (nluns = i = 0; i < FSG_MAX_LUNS; ++i)
> + if (common->luns[i])
> + nluns = i + 1;
> + if (!nluns)
> + pr_warn("No LUNS defined, continuing anyway\n");
> + else
> + common->nluns = nluns;
> + pr_info("Number of LUNs=%u\n", common->nluns);
> + }
>
> It iterates over all luns and if lun is non-NULL it sets nluns to index
> of that lun plus one. So if luns[0], lun[1], lun[2], lun[3] and lun[5]
> are set, common->nluns = 6.
>
Yeah I see it now. What I wrote was a problem before your patch but now
it seams to be ok, just nluns name is very misleading. Summing up, just
like you wrote this patch should not go to stable.
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2015-07-20 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 14:57 [PATCH v3 0/5] Mass storage fixes and improvements Krzysztof Opasiak
2015-07-07 14:57 ` [PATCH v3 1/5] usb: gadget: mass_storage: Free buffers if create lun fails Krzysztof Opasiak
2015-07-07 14:57 ` [PATCH v3 2/5] usb: gadget: mass_storage: Place EXPORT_SYMBOL_GPL() after func definition Krzysztof Opasiak
2015-07-07 14:57 ` [PATCH v3 3/5] usb: gadget: storage-common: Set FSG_MAX_LUNS to 16 Krzysztof Opasiak
2015-07-07 22:08 ` Sergei Shtylyov
2015-07-07 14:57 ` [PATCH v3 4/5] usb: gadget: mass_storage: Use static array for luns Krzysztof Opasiak
2015-07-08 14:00 ` Michal Nazarewicz
2015-07-20 10:34 ` Krzysztof Opasiak
2015-07-20 13:17 ` Michal Nazarewicz
2015-07-20 14:09 ` Krzysztof Opasiak [this message]
2015-07-20 15:16 ` Michal Nazarewicz
2015-07-07 14:57 ` [PATCH v3 5/5] usb: gadget: mass_storage: Warn if LUNs ids are not contiguous Krzysztof Opasiak
2015-07-08 14:01 ` Michal Nazarewicz
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=55AD0121.4070107@samsung.com \
--to=k.opasiak@samsung.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=david.fisher1@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mina86@mina86.com \
--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 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.