Which patch(es) should I try? Should I combine both Alexander's and
Andrea's together? Should I try turning off SMP to verify SMP is the
problem?
Thanks
--Michael
syslogd logging below:
Mar 1 07:09:48 spider kernel: swap_duplicate at cc00: entry 0000cc00,
unused page
Mar 1 07:09:48 spider kernel: swap_free: swap-space map bad (entry
0000cc00)
Mar 1 07:09:48 spider kernel:
Mar 1 07:09:48 spider kernel: Out of memory for indexer.
Mar 1 07:10:01 spider kernel: swap_duplicate at ff00: entry 0000ff00,
unused page
Mar 1 07:10:01 spider kernel: swap_free: swap-space map bad (entry
0000ff00)
Mar 1 07:10:01 spider kernel:
Mar 1 07:10:01 spider kernel: Out of memory for indexer.
On Mon, 1 Mar 1999, Alexander Viro wrote:
>
>
> On Mon, 1 Mar 1999, Andrea Arcangeli wrote:
>
> > As first the fix from Alexander (the one that uses a gc_current with my
> > further cleanup) seems SMP safe and works fine here. At least I am not
> > been able to cause any problem to the kernel so far here.
> >
> > But playing still more the unix domain socket code some minutes ago I
> > discovered new critical issues.
> >
> > I discovered a way to leak memory and cause the machine to stall completly
> > in kernel mode for minutes as normal user. Waiting a bit more it will eat
> > all memory and the machine will crash badly. It's a plain security issue.
>
> Yes, you can do it. I don't think that ENOMEM is the right return value
> here - ECONNREFUSED is more reasonable, IMHO. But yes, we need to limit
> the backlog to avoid DoS.
>
> I'm not sure that it's what Michael had triggered - it looked rather like
> a dangling pointers with following stomping the random pieces of core.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/