> Pools are generally (thought) safe from use after free bugs because
> the poison renders the object useless. Unfortunately, in some cases
> pool will very quickly recycle an object, meaning the newly allocated
> object may be reinitialzed and then appear sensible to the code
> holding on to the "
On Sun, Apr 13, 2014 at 3:00 PM, Abel Abraham Camarillo Ojeda <
acam...@verlet.org> wrote:
> On Tue, Apr 8, 2014 at 9:44 PM, Abel Abraham Camarillo Ojeda
> wrote:
> > well, I didn't mentioned it I already tried that -disable radeondrm-
> > with -current,
> > didn't work, will try again to provide
Pools are generally (thought) safe from use after free bugs because
the poison renders the object useless. Unfortunately, in some cases
pool will very quickly recycle an object, meaning the newly allocated
object may be reinitialzed and then appear sensible to the code
holding on to the "old" point
On Sun, Apr 13, 2014 at 8:00 AM, Abel Abraham Camarillo Ojeda
wrote:
> On Tue, Apr 8, 2014 at 9:44 PM, Abel Abraham Camarillo Ojeda
> wrote:
>> well, I didn't mentioned it I already tried that -disable radeondrm-
>> with -current,
>> didn't work, will try again to provide log file...
>>
>> As soo
I took another look at the way junk works in malloc, and there's a few
improvements I'd like to make.
1. Remove the Z option. In general, I think malloc options should make
programs crash more, not less. This option is a bandaid, but looks
like something that makes things better. (Anecdotally, I'v
On Sun, Apr 13, 2014 at 22:24, Stuart Henderson wrote:
> These values make sense to me, though I think some people didn't like
> daemons themselves changing rlimit when this came up before, so we added
> a login.conf section when this was needed for bgpd (handled by rc.subr
> setting the class auto
>> Index: nginx.conf
>> ===
>> RCS file: /cvs/src/usr.sbin/nginx/conf/nginx.conf,v
>> retrieving revision 1.18
>> diff -u -p -r1.18 nginx.conf
>> --- nginx.conf 27 Mar 2014 10:40:42 - 1.18
>> +++ nginx.conf 13 Apr
On 2014/04/13 16:56, Ted Unangst wrote:
> Recently had a bit of an issue with the default nginx.conf and running
> out of files. By default, login.conf imposes a limit of 128 files,
> which is not nearly sufficient to process the configured 1024
> connections.
>
> We need to fix two things. First,
> Recently had a bit of an issue with the default nginx.conf and running
> out of files. By default, login.conf imposes a limit of 128 files,
> which is not nearly sufficient to process the configured 1024
> connections.
Right.
> We need to fix two things. First, raise the file limit to 1024.
> S
Recently had a bit of an issue with the default nginx.conf and running
out of files. By default, login.conf imposes a limit of 128 files,
which is not nearly sufficient to process the configured 1024
connections.
We need to fix two things. First, raise the file limit to 1024.
Second, lower the con
On Tue, Apr 8, 2014 at 9:44 PM, Abel Abraham Camarillo Ojeda
wrote:
> well, I didn't mentioned it I already tried that -disable radeondrm-
> with -current,
> didn't work, will try again to provide log file...
>
> As soon as I can get home ...
>
> On Tue, Apr 8, 2014 at 5:46 PM, Mike Larki
11 matches
Mail list logo