From: walter harms <wharms@bfs.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] cifs: small underflow in cnvrtDosUnixTm()
Date: Fri, 28 Apr 2017 14:57:37 +0000 [thread overview]
Message-ID: <59035861.8050101@bfs.de> (raw)
In-Reply-To: <20170428144129.3v3fcz5oldjtmymx@mwanda>
Am 28.04.2017 16:41, schrieb Dan Carpenter:
> On Fri, Apr 28, 2017 at 04:40:04PM +0200, walter harms wrote:
>>
>>
>> Am 28.04.2017 14:51, schrieb Dan Carpenter:
>>> January is month 1. There is no zero-th month. If someone passes a
>>> zero month then it means we read from one space before the start of the
>>> total_days_of_prev_months[] array.
>>>
>>> We may as well also be strict about days as well.
>>>
>>> Fixes: 1bd5bbcb6531 ("[CIFS] Legacy time handling for Win9x and OS/2 part 1")
>>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>> ---
>>> v2: Be strict about days as well. My first patch was less intrusive
>>> because it only prevented the out of bounds access. I have no idea how
>>> common it is to pass in an illegal day but, hopefully, not very common.
>>>
>>> diff --git a/fs/cifs/netmisc.c b/fs/cifs/netmisc.c
>>> index abae6dd2c6b9..4b2726ee4fad 100644
>>> --- a/fs/cifs/netmisc.c
>>> +++ b/fs/cifs/netmisc.c
>>> @@ -980,10 +980,10 @@ struct timespec cnvrtDosUnixTm(__le16 le_date, __le16 le_time, int offset)
>>> cifs_dbg(VFS, "illegal hours %d\n", st->Hours);
>>> days = sd->Day;
>>> month = sd->Month;
>>> - if ((days > 31) || (month > 12)) {
>>> + if (days < 1 || days > 31 || month < 1 || month > 12) {
>>> cifs_dbg(VFS, "illegal date, month %d day: %d\n", month, days);
>>> - if (month > 12)
>>> - month = 12;
>>> + days = (days < 1) ? 1 : ((days <= 31) ? days : 31);
>>> + month = (month < 1) ? 1 : ((month <= 12) ? month : 12);
>>> }
>>> month -= 1;
>>> days += total_days_of_prev_months[month];
>>
>> The mixing in now a bit unfortunate ... why not simply
>>
>> if (days < 1 || days > 31 || month < 1 || month > 12)
>> cifs_dbg(VFS, "illegal date, month %d day: %d\n", month, days);
>>
>> month = (month < 1) ? 1 : ((month <= 12) ? month : 12);
>> days = (days < 1) ? 1 : ((days <= 31) ? days : 31);
>>
>
> I prefer my version because I feel like it more closely expresses what
> I want to say.
>
(Actually it is your code just without the braces.)
what is about differentiating between day and month ?
if (days < 1 || days > 31) {
cifs_dbg(VFS, "illegal day: %d\n", days);
days = (days < 1) ? 1 : 31 ;
}
if ( month < 1 || month > 12) {
cifs_dbg(VFS, "illegal month %d\n", month);
month = (month < 1) ? 1 : 12 ;
}
this way you have a obvious error handling for day and month.
I still like my first version even when day/month are recalculated every
time the flow is very linear only the error message is a deviation.
(Given that ?: makes it not easy to digest)
re,
wh
next prev parent reply other threads:[~2017-04-28 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 13:49 [PATCH] cifs: small underflow in cnvrtDosUnixTm() Dan Carpenter
2017-04-28 12:51 ` [PATCH v2] " Dan Carpenter
2017-04-28 14:40 ` walter harms
[not found] ` <59035444.6090305-fPG8STNUNVg@public.gmane.org>
2017-04-28 14:41 ` Dan Carpenter
2017-04-28 14:57 ` walter harms [this message]
[not found] ` <59035861.8050101-fPG8STNUNVg@public.gmane.org>
2017-04-29 18:49 ` Dan Carpenter
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=59035861.8050101@bfs.de \
--to=wharms@bfs.de \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.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