From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Paul Moore <paul@paul-moore.com>, Stephen Smalley <sds@tycho.nsa.gov>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Eric Paris <eparis@parisplace.org>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
William Roberts <william.c.roberts@intel.com>,
selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: selinux: Fix an uninitialized variable bug in range_read()
Date: Sat, 1 Apr 2017 08:40:59 +0200 [thread overview]
Message-ID: <fb1cb81c-4b03-5b21-f933-ea3e58491a13@users.sourceforge.net> (raw)
In-Reply-To: <CAHC9VhT7njoVyHgyiTQhCcvZEYrTE_XZRLxT4+JJPiH3W88AUw@mail.gmail.com>
>>> We removed this initialization as a cleanup but it is probably
>>> required.
>>>
>>> The concern is that "nel" can be zero. I'm not an expert on SELinux
>>> code but I think it looks possible to write an SELinux policy which
>>> triggers this bug. GCC doesn't catch this, but my static checker
>>> does.
>>>
>>> Fixes: 9c312e79d6af ("selinux: Delete an unnecessary variable
>>> initialisation in range_read()")
>>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>
>> Nice catch, thanks!
>>
>> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
>
> Yes, indeed. Thanks Dan, I should have caught this when merging Markus' patch.
How do you think about the possibility to call the function “range_read” only with
a system configuration where the interface “le32_to_cpu” will be resolved to
a positive value so that statements in the corresponding for loop will be executed
at least once?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-security-module@vger.kernel.org
Subject: Re: selinux: Fix an uninitialized variable bug in range_read()
Date: Sat, 01 Apr 2017 06:40:59 +0000 [thread overview]
Message-ID: <fb1cb81c-4b03-5b21-f933-ea3e58491a13@users.sourceforge.net> (raw)
In-Reply-To: <CAHC9VhT7njoVyHgyiTQhCcvZEYrTE_XZRLxT4+JJPiH3W88AUw@mail.gmail.com>
>>> We removed this initialization as a cleanup but it is probably
>>> required.
>>>
>>> The concern is that "nel" can be zero. I'm not an expert on SELinux
>>> code but I think it looks possible to write an SELinux policy which
>>> triggers this bug. GCC doesn't catch this, but my static checker
>>> does.
>>>
>>> Fixes: 9c312e79d6af ("selinux: Delete an unnecessary variable
>>> initialisation in range_read()")
>>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>
>> Nice catch, thanks!
>>
>> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
>
> Yes, indeed. Thanks Dan, I should have caught this when merging Markus' patch.
How do you think about the possibility to call the function “range_read” only with
a system configuration where the interface “le32_to_cpu” will be resolved to
a positive value so that statements in the corresponding for loop will be executed
at least once?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: linux-security-module@vger.kernel.org
Subject: selinux: Fix an uninitialized variable bug in range_read()
Date: Sat, 1 Apr 2017 08:40:59 +0200 [thread overview]
Message-ID: <fb1cb81c-4b03-5b21-f933-ea3e58491a13@users.sourceforge.net> (raw)
In-Reply-To: <CAHC9VhT7njoVyHgyiTQhCcvZEYrTE_XZRLxT4+JJPiH3W88AUw@mail.gmail.com>
>>> We removed this initialization as a cleanup but it is probably
>>> required.
>>>
>>> The concern is that "nel" can be zero. I'm not an expert on SELinux
>>> code but I think it looks possible to write an SELinux policy which
>>> triggers this bug. GCC doesn't catch this, but my static checker
>>> does.
>>>
>>> Fixes: 9c312e79d6af ("selinux: Delete an unnecessary variable
>>> initialisation in range_read()")
>>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>
>> Nice catch, thanks!
>>
>> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
>
> Yes, indeed. Thanks Dan, I should have caught this when merging Markus' patch.
How do you think about the possibility to call the function ?range_read? only with
a system configuration where the interface ?le32_to_cpu? will be resolved to
a positive value so that statements in the corresponding for loop will be executed
at least once?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-04-01 6:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 15:21 [PATCH] selinux: Fix an uninitialized variable bug Dan Carpenter
2017-03-31 15:21 ` Dan Carpenter
2017-03-31 15:21 ` Dan Carpenter
2017-03-31 15:52 ` Stephen Smalley
2017-03-31 15:52 ` Stephen Smalley
2017-03-31 15:52 ` Stephen Smalley
2017-03-31 19:18 ` Paul Moore
2017-03-31 19:18 ` Paul Moore
2017-03-31 19:18 ` Paul Moore
2017-04-01 6:40 ` SF Markus Elfring [this message]
2017-04-01 6:40 ` selinux: Fix an uninitialized variable bug in range_read() SF Markus Elfring
2017-04-01 6:40 ` SF Markus Elfring
2017-04-01 14:52 ` Paul Moore
2017-04-01 14:52 ` Paul Moore
2017-04-01 14:52 ` Paul Moore
2017-04-03 1:10 ` [PATCH] selinux: Fix an uninitialized variable bug James Morris
2017-04-03 1:10 ` James Morris
2017-04-03 1:10 ` James Morris
2017-04-03 21:45 ` Paul Moore
2017-04-03 21:45 ` Paul Moore
2017-04-03 21:45 ` Paul Moore
2017-04-04 0:03 ` James Morris
2017-04-04 0:03 ` James Morris
2017-04-04 0:03 ` James Morris
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=fb1cb81c-4b03-5b21-f933-ea3e58491a13@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=dan.carpenter@oracle.com \
--cc=eparis@parisplace.org \
--cc=james.l.morris@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=william.c.roberts@intel.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 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.