All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [PATCH] env: mmc: Correct partition comparison in mmc_offset_try_partition
Date: Thu, 12 Nov 2020 08:34:27 +0900	[thread overview]
Message-ID: <028f53ca-2251-0bf0-37ed-49e1cf213cbd@samsung.com> (raw)
In-Reply-To: <CAL9K-_g7J8yyZ_wbDnEVCP-r8+jj2v0adtm=2dY-O9OoOstwZA@mail.gmail.com>

Hi,

On 11/11/20 7:25 PM, ????? wrote:
> On Wed, Nov 11, 2020 at 7:07 PM Jorge Ramirez-Ortiz, Gmail
> <jorge.ramirez.ortiz@gmail.com> wrote:
>>
>> On 11/11/20, Jaehoon Chung wrote:
>>> On 11/10/20 11:28 PM, Hoyeonjiki Kim wrote:
>>>> The function mmc_offset_try_partition searches MMC partition to save the
>>>> environment data by name.  However, it only compares the first word-size
>>>> bytes (size of 'const char *'), which may make the function to find
>>>> unintended partition.
>>>>
>>>> Correct the function not to partially compare the partition name with
>>>> config "u-boot,,mmc-env-partition".
>>>>
>>>> Signed-off-by: Hoyeonjiki Kim <jigi.kim@gmail.com>
>>>> ---
>>>>  env/mmc.c | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/env/mmc.c b/env/mmc.c
>>>> index 4e67180b23..505f7aa2b8 100644
>>>> --- a/env/mmc.c
>>>> +++ b/env/mmc.c
>>>> @@ -42,7 +42,7 @@ static inline int mmc_offset_try_partition(const char *str, int copy, s64 *val)
>>>>             if (ret < 0)
>>>>                     return ret;
>>>>
>>>> -           if (!strncmp((const char *)info.name, str, sizeof(str)))
>>>> +           if (!strcmp((const char *)info.name, str))
>>>
>>> Using "strlen(str)" is better than changing to strcmp.
>>>
>>> strncmp(..., ..., strlen(str))
>>
>> absolutely.
>> maybe also modify the commit like to indicate a fix to the current bug?
> 
> Thanks for the feedback for both.
> 
> However, when we do so, isn't there still the possibility for the
> function searching incorrect partition if,
> 1) "str" is shorter than "info.name", and
> 2) the first "strlen(str)" letters of "info.name" is same with those of "str"?

Make sense. You're right. :)

There are two approach. One is that choose one of those length what is longer.
Other is your approach. I don't have any objection to fix whatever.

Just resend your patch with Jorge's comment, plz. 


Best Regards,
Jaehoon Chung

> 
> This commit is for fixing the current bug, but also I wanna make sure
> that partition name matches fully.
> 
> Let me know your opinion.
> 
> Best Regards,
> Hoeyonjiki Kim
> 
>>
>>>
>>>
>>> Best Regards,
>>> Jaehoon Chung
>>>
>>>>                     break;
>>>>     }
>>>>
>>>>
>>>
> 

  reply	other threads:[~2020-11-11 23:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20201110211937epcas1p4e9a17e37a7362b2453fc9b14706d3b17@epcas1p4.samsung.com>
2020-11-10 14:28 ` [PATCH] env: mmc: Correct partition comparison in mmc_offset_try_partition Hoyeonjiki Kim
2020-11-11  8:09   ` Jaehoon Chung
2020-11-11 10:07     ` Jorge
2020-11-11 10:25       ` 김호연지기
2020-11-11 23:34         ` Jaehoon Chung [this message]
2020-11-12 11:08           ` Hoyeonjiki Kim
2020-11-12 20:01     ` Wolfgang Denk
2020-11-16  3:06       ` Jaehoon Chung
2020-11-12 12:30 Hoyeonjiki Kim
2020-11-12 13:11 ` Hoyeonjiki Kim
2020-11-12 20:06 ` Wolfgang Denk
2020-11-13  4:10   ` Hoyeonjiki Kim

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=028f53ca-2251-0bf0-37ed-49e1cf213cbd@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=u-boot@lists.denx.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 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.