Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-07-21 Thread Maxime Villard
Hi, I put here a bug among others: - sys/kern/kern_exec.c - char *pathbuf = NULL; [...] pathbuf = pool_get(&namei_pool, PR_WAITOK); [...] /* setup new registers and do misc. setup. */ if (p

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-07-21 Thread Ville Valkonen
On Jul 21, 2015 9:32 AM, "Maxime Villard" wrote: > > Hi, > I put here a bug among others: > > - sys/kern/kern_exec.c - > > char *pathbuf = NULL; > > [...] > > pathbuf = pool_get(&namei_pool, PR_WAITOK); > > [..

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-07-21 Thread Alexey Suslikov
Ville Valkonen gmail.com> writes: > On Jul 21, 2015 9:32 AM, "Maxime Villard" m00nbsd.net> wrote: > > It is not the last bug Brainy has found, but it is the last one I > > report. I don't have time for that. > > > > Maxime > > Why such a dramatic tone? Because that famous "thank you small peop

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-07-21 Thread sam
On Tue, 21 Jul 2015 11:31:44 +0200 Maxime Villard wrote: > Found by The Brainy Code Scanner. > > It is not the last bug Brainy has found, but it is the last one I > report. I don't have time for that. > How about you release the Brainy Code Scanner then? "I have so many bugs; in fact, there a

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-07-21 Thread Alexey Suslikov
sam cmpct.info> writes: > How about you release the Brainy Code Scanner then? > > "I have so many bugs; in fact, there are so many, I don't even have the > time to report them! My scanner is so good!" > > Or perhaps you should report 'just' the relatively important ones? Made my day. Searchin

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-07 Thread Maxime Villard
Well, I guess I'll have to admit that I find your attitude extremely disrespectful. But I don't tend to feel particularly offended by this kind of things, so it probably does not matter. Le 21/07/2015 12:31, sam a écrit : On Tue, 21 Jul 2015 11:31:44 +0200 Maxime Villard wrote: Found by The

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-07 Thread Chris Cappuccio
Maxime Villard [m...@m00nbsd.net] wrote: > > Now, I believe that this effort is too much for my spare time. If you > want to say "thanks" to me for reporting this vulnerability, dear Sam, > it's never too late. > I put here a thanks among others: Thank you for your effort to help improve the Op

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-07 Thread shun . obsd . tech
Hi Maxime, Hi Sam, I have been following this thread (and others) for some time. On Fri, Aug 07, 2015 at 09:55:21PM +0200, Maxime Villard wrote: > Well, I guess I'll have to admit that I find your attitude extremely > disrespectful. I have to agree that the emails are rather short and tend to lac

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-07 Thread Christian Schulte
Am 08/07/15 um 21:55 schrieb Maxime Villard: Developing, improving and maintaining Brainy takes time and energy, as well as investigating and packaging the bugs and vulnerabilities it finds. I've so far sent some reports here just because I'm "friendly" enough, and because modifying a few things

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-07 Thread Alexey Suslikov
Christian Schulte schulte.it> writes: > > Now, I believe that this effort is too much for my spare time. > > Then why not release that scanner? That effort could be shared. What's > so secret about it? You have been asked several times already. Start sharing right now. Brainy OpenBSD page cont

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Marcus MERIGHI
ch...@nmedia.net (Chris Cappuccio), 2015.08.07 (Fri) 22:34 (CEST): > Maxime Villard [m...@m00nbsd.net] wrote: > > Now, I believe that this effort is too much for my spare time. If you > > want to say "thanks" to me for reporting this vulnerability, dear Sam, > > it's never too late. > > I put here

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Christian Schulte
Am 08/07/15 um 23:46 schrieb Alexey Suslikov: Christian Schulte schulte.it> writes: Now, I believe that this effort is too much for my spare time. Then why not release that scanner? That effort could be shared. What's so secret about it? You have been asked several times already. Start sha

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Ville Valkonen
Hello Maxime, On Aug 7, 2015 10:56 PM, "Maxime Villard" wrote: > > Well, I guess I'll have to admit that I find your attitude extremely > disrespectful. But I don't tend to feel particularly offended by this > kind of things, so it probably does not matter. > > > > Le 21/07/2015 12:31, sam a écri

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Alexey Suslikov
On Sat, Aug 8, 2015 at 2:21 PM, Christian Schulte wrote: > Am 08/07/15 um 23:46 schrieb Alexey Suslikov: >> >> Christian Schulte schulte.it> writes: >> Now, I believe that this effort is too much for my spare time. >>> >>> >>> Then why not release that scanner? That effort could be shared. W

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Christian Schulte
Am 08/08/15 um 15:06 schrieb Alexey Suslikov: On Sat, Aug 8, 2015 at 2:21 PM, Christian Schulte wrote: Am 08/07/15 um 23:46 schrieb Alexey Suslikov: Christian Schulte schulte.it> writes: Now, I believe that this effort is too much for my spare time. Then why not release that scanner? Th

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-09 Thread Philip Guenther
Awful lot of noise wherein people tell someone else what they should need to do with their time and their code. To the best of my knowledge, we've cited and/or thanked Maxime in the commits fixing the issues he's found, and we're glad to continue to receive his reports, whether or not they includ

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-09 Thread Theo de Raadt
> Awful lot of noise wherein people tell someone else what they should > need to do with their time and their code. > > > To the best of my knowledge, we've cited and/or thanked Maxime in the > commits fixing the issues he's found, and we're glad to continue to > receive his reports, whether or n

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-09 Thread Christian Schulte
Am 08/09/15 um 23:38 schrieb Theo de Raadt: Awful lot of noise wherein people tell someone else what they should need to do with their time and their code. Sorry. It wasn't meant that way. I was just trying to be helpful to someone saying "I don't have time for that" and "this effort is too mu

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-09 Thread Alexey Suslikov
Theo de Raadt cvs.openbsd.org> writes: > I would like to point out the noise is coming from *users* -- not from > actual developers in the project. http://www.imdb.com/title/tt1278449/ you'll get the idea.

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-10 Thread sam
I'm sorry, I misread you. I wasn't trying to make fun of you or disregard your work. Thanks for reporting this (among other bugs). I am also of the opinion that if somebody/a method can discover bugs, they should report them. And if they can't, that method should be disclosed to allow others to

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-10 Thread sam
On Fri, 7 Aug 2015 22:49:50 +0200 shun.obsd.t...@dropcut.net wrote: > Hi Maxime, > Hi Sam, > > I have been following this thread (and others) for some time. > > On Fri, Aug 07, 2015 at 09:55:21PM +0200, Maxime Villard wrote: > > Well, I guess I'll have to admit that I find your attitude extremel

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-10 Thread Stuart Henderson
On 2015/08/10 11:54, sam wrote: > I am also of the opinion that if somebody/a method can discover bugs, > they should report them. And if they can't, that method should be > disclosed to allow others to continue their work. So you think others "should" do work for you, right? Whether that work is

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-10 Thread Theo de Raadt
> I am also of the opinion that if somebody/a method can discover bugs, > they should report them. And if they can't, that method should be > disclosed to allow others to continue their work. And my opinion is that Sam should back his opinions with lots of money.

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-10 Thread Theo de Raadt
> It feels wasteful to develop a seemingly comprehensive and modular code > scanner which will inherently find heaps of bugs, and then not release > it or allow others to work with it. Sam, since you think throwing opinions out there is valuable Let me give me yours. I think you should talk priv

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-12 Thread Артур Истомин
On Sun, Aug 09, 2015 at 03:38:25PM -0600, Theo de Raadt wrote: > > Awful lot of noise wherein people tell someone else what they should > > need to do with their time and their code. > > > > > > To the best of my knowledge, we've cited and/or thanked Maxime in the > > commits fixing the issues he

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-12 Thread Артур Истомин
On Mon, Aug 10, 2015 at 12:23:44PM +0100, Stuart Henderson wrote: > On 2015/08/10 11:54, sam wrote: > > I am also of the opinion that if somebody/a method can discover bugs, > > they should report them. And if they can't, that method should be > > disclosed to allow others to continue their work. >

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-12 Thread Stuart Henderson
On 2015/08/12 17:10, Артур Истомин wrote: > On Mon, Aug 10, 2015 at 12:23:44PM +0100, Stuart Henderson wrote: > > On 2015/08/10 11:54, sam wrote: > > > I am also of the opinion that if somebody/a method can discover bugs, > > > they should report them. And if they can't, that method should be > > >

sys/arch/{hppa,hppa64}/dev/apic.c cosmetics, Was:Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-09 Thread Alexey Suslikov
Christian Schulte schulte.it> writes: > _14/ UNINITIALIZED VARIABLE: sys/arch/hppa64/dev/apic.c rev1.8 > At l.176, 'cnt' is not initialized. I came up with the following. --- sys/arch/hppa/dev/apic.c.orig Sun Aug 9 14:16:56 2015 +++ sys/arch/hppa/dev/apic.cSun Aug 9 14:30:47 2

Possible memory leak in sys/dev/ic/ti.c (was: Re: Brainy: User-Triggerable Kernel Memory Leak in execve())

2015-08-08 Thread Christian Schulte
While at it. I cannot test this as I do not have corresponding hardware. Index: sys/dev/ic/ti.c === RCS file: /cvs/src/sys/dev/ic/ti.c,v retrieving revision 1.12 diff -u -r1.12 ti.c --- sys/dev/ic/ti.c 22 Dec 2014 02:28:51 -

Re: Possible memory leak in sys/dev/ic/ti.c (was: Re: Brainy: User-Triggerable Kernel Memory Leak in execve())

2015-08-09 Thread Sebastien Marie
Hi, On Sat, Aug 08, 2015 at 05:39:07PM +0200, Christian Schulte wrote: > While at it. I cannot test this as I do not have corresponding hardware. > > Index: sys/dev/ic/ti.c > === > RCS file: /cvs/src/sys/dev/ic/ti.c,v > retrieving re