linux-kernel - Re: [next] unix stream crashes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 01 Sep 2011 18:40:45 -0700
From:	Tim Chen <tim.c.chen@...ux.intel.com>
To:	Valdis.Kletnieks@...edu
Cc:	Jiri Slaby <jirislaby@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	ML netdev <netdev@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [next] unix stream crashes

On Thu, 2011-09-01 at 20:49 -0400, Valdis.Kletnieks@...edu wrote:
> On Thu, 01 Sep 2011 22:46:32 +0200, Jiri Slaby said:
> > Hi,
> > 
> > my box 100% crashes when booting. It's both in unix socket recv and send 
> > paths. I've reverted 0856a30409 (Scm: Remove unnecessary pid & 
> > credential references in Unix socket's send and receive path) and it 
> > seems to help.
> > 
> > The oops:
> > http://www.fi.muni.cz/~xslaby/sklad/panics/af_unix_crash.png
> 
> I was seeing a 100% repeatable crash with the X server starting as well, but
> wasn't able to get a traceback because my X server was doing the modeset before
> it crashed (so all I got was a black screen) and netconsole is busticated for
> me.  I can confirm that reverting that one commit allows my box to boot and get
> X up and running as well.
> 

Yes, Jiri's log does indicate that something went wrong when releasing
the skb, most likely due to changes in the pid and credentials ref
count.  Unfortunately, I cannot duplicate the problem on my system.  Any
info on your system to help me debug will be appreciated.  I'll try to
take another look at the patch tomorrow.

Tim

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/