3.13.11-ckt36 -stable review patch. If anyone has any objections, please let
me know.
---8<
From: Eric Dumazet
commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b upstream.
Dmitry reported a struct pid leak detected by a syzkaller progr
3.19.8-ckt16 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Eric Dumazet
commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b upstream.
Dmitry reported a struct pid leak detected by a syzkaller progra
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Eric Dumazet
[ Upstream commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b ]
Dmitry reported a struct pid leak detected by a syzkaller progr
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b upstream.
Dmitry reported a struct pid leak detected by a syzkaller program.
Bug happens in unix_stream_recvmsg() when we brea
From: Eric Dumazet
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b ]
Dmitry reported a struct pid leak detected by a syzkaller program.
Bug happens in unix_stream_recvmsg() when we break th
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b ]
Dmitry reported a struct pid leak detected by a syzkaller program.
Bug happens in unix_stream_recvmsg() when we break
3.16.7-ckt25 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Eric Dumazet
commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b upstream.
Dmitry reported a struct pid leak detected by a syzkaller progra
On Wed, Feb 24, 2016 at 09:24:39PM +, Ben Hutchings wrote:
(...)
> Yes, it looks like the bug was really introduced way back in 2.5.65 by
> "[NET]: Simplify scm handling and sendmsg/recvmsg invocation,
> consolidate net compat syscalls."
>
> So I think this is also needed for 2.6.32.
Thanks f
On Tue, 2016-02-23 at 22:07 +, Rainer Weikusat wrote:
> Ben Hutchings writes:
> > 3.2.78-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Eric Dumazet
> >
> > commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b upstream.
>
> [...]
>
Ben Hutchings writes:
> 3.2.78-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Eric Dumazet
>
> commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b upstream.
[...]
> Fixes: b3ca9b02b007 ("net: fix multithreaded signal handling in unix recv
> ro
3.2.78-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit fa0dc04df259ba2df3ce1920e9690c7842f8fa4b upstream.
Dmitry reported a struct pid leak detected by a syzkaller program.
Bug happens in unix_stream_recvmsg() when we break the
Hi Eric,
On Sun, Jan 24, 2016 at 01:53:50PM -0800, Eric Dumazet wrote:
> From: Eric Dumazet
>
> Dmitry reported a struct pid leak detected by a syzkaller program.
>
> Bug happens in unix_stream_recvmsg() when we break the loop when a
> signal is pending, without properly releasing scm.
>
> Fix
From: Eric Dumazet
Dmitry reported a struct pid leak detected by a syzkaller program.
Bug happens in unix_stream_recvmsg() when we break the loop when a
signal is pending, without properly releasing scm.
Fixes: b3ca9b02b007 ("net: fix multithreaded signal handling in unix recv
routines")
Repor
On Sat, Jan 23, 2016 at 7:04 PM, Willy Tarreau wrote:
> On Sat, Jan 23, 2016 at 06:50:11PM -0800, Eric Dumazet wrote:
>> On Sat, Jan 23, 2016 at 6:38 PM, Willy Tarreau wrote:
>> > On Sun, Jan 24, 2016 at 03:11:45AM +0100, Willy Tarreau wrote:
>> >> It doesn't report this on 3.10.
>> >
>> > To be
On Sat, Jan 23, 2016 at 06:50:11PM -0800, Eric Dumazet wrote:
> On Sat, Jan 23, 2016 at 6:38 PM, Willy Tarreau wrote:
> > On Sun, Jan 24, 2016 at 03:11:45AM +0100, Willy Tarreau wrote:
> >> It doesn't report this on 3.10.
> >
> > To be more precise, kmemleak reports the issue on 3.13 and not on 3.
On Sat, Jan 23, 2016 at 6:38 PM, Willy Tarreau wrote:
> On Sun, Jan 24, 2016 at 03:11:45AM +0100, Willy Tarreau wrote:
>> It doesn't report this on 3.10.
>
> To be more precise, kmemleak reports the issue on 3.13 and not on 3.12.
> I'm not sure if it's reliable enough to run a bisect though.
>
> W
On Sun, Jan 24, 2016 at 03:11:45AM +0100, Willy Tarreau wrote:
> It doesn't report this on 3.10.
To be more precise, kmemleak reports the issue on 3.13 and not on 3.12.
I'm not sure if it's reliable enough to run a bisect though.
Willy
On Sat, Jan 23, 2016 at 07:46:45PM +0100, Dmitry Vyukov wrote:
> On Sat, Jan 23, 2016 at 7:40 PM, Willy Tarreau wrote:
> > On Sat, Jan 23, 2016 at 07:14:33PM +0100, Dmitry Vyukov wrote:
> >> I've attached my .config.
> >> Also run this program in a parallel loop. I think it's leaking not
> >> ever
On Sat, Jan 23, 2016 at 10:46 AM, Dmitry Vyukov wrote:
> On Sat, Jan 23, 2016 at 7:40 PM, Willy Tarreau wrote:
>> On Sat, Jan 23, 2016 at 07:14:33PM +0100, Dmitry Vyukov wrote:
>>> I've attached my .config.
>>> Also run this program in a parallel loop. I think it's leaking not
>>> every time, pro
On Sat, Jan 23, 2016 at 7:40 PM, Willy Tarreau wrote:
> On Sat, Jan 23, 2016 at 07:14:33PM +0100, Dmitry Vyukov wrote:
>> I've attached my .config.
>> Also run this program in a parallel loop. I think it's leaking not
>> every time, probably some race is involved.
>
> Thank you. Just in order to c
On Sat, Jan 23, 2016 at 07:14:33PM +0100, Dmitry Vyukov wrote:
> I've attached my .config.
> Also run this program in a parallel loop. I think it's leaking not
> every time, probably some race is involved.
Thank you. Just in order to confirm, am I supposed to see the
messages you quoted in dmesg ?
Hi Eric, Dmitry,
On Fri, Jan 22, 2016 at 08:50:01AM -0800, Eric Dumazet wrote:
> CC netdev, as it looks some af_unix issue ...
>
> On Fri, 2016-01-22 at 16:08 +0100, Dmitry Vyukov wrote:
> > Hello,
> >
> > The following program causes struct pid memory leak:
&
CC netdev, as it looks some af_unix issue ...
On Fri, 2016-01-22 at 16:08 +0100, Dmitry Vyukov wrote:
> Hello,
>
> The following program causes struct pid memory leak:
>
> // autogenerated by syzkaller (http://github.com/google/syzkaller)
> #include
> #include
&
Hello,
The following program causes struct pid memory leak:
// autogenerated by syzkaller (http://github.com/google/syzkaller)
#include
#include
#include
#include
#include
long r[37];
void* thr(void* arg)
{
switch ((long)arg) {
case 0:
r[0] = syscall(SYS_mmap, 0x2000ul
24 matches
Mail list logo
