[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200508154737.GA25182@voyager>
Date: Fri, 8 May 2020 17:47:37 +0200
From: Markus Wichmann <nullplan@....net>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] fix coredump when sched_rr_get_interval parameter
ts is NULL
On Fri, May 08, 2020 at 02:46:56PM +0000, zhuyan (M) wrote:
> In function sched_rr_get_interval, there is a risk of null pointer reference. On line 12, when ts is NULL, dereferencing the null pointer will cause the program coredump.
>
> Therefore, it must ensure that ts is not empty before use.
>
Is calling this function with a NULL pointer sensible? The manpage
certainly doesn't say so. Usually policy in musl is to not fix
application bugs, but to dereference pointers without NULL pointer check
unless there is an explicit requirement in the relevant standards that a
NULL pointer be accepted.
Ciao,
Markus
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
