netdev - Re: ax25_recvmsg lockup

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130804002520.GA10206@redhat.com>
Date:	Sat, 3 Aug 2013 20:25:20 -0400
From:	Dave Jones <davej@...hat.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: ax25_recvmsg lockup

On Sat, Aug 03, 2013 at 01:46:04PM -0700, David Miller wrote:
 > From: Dave Jones <davej@...hat.com>
 > Date: Mon, 17 Jun 2013 10:28:03 -0400
 > 
 > > With the right arguments from userspace, reading from an ax25 socket
 > > can spend long enough in the kernel that it triggers the softlockup
 > > detector.  I hit a bunch of these traces in a trinity run that I
 > > left running over the weekend.
 > 
 > I looked at this a bunch of times and am still mystified how this
 > can happen.
 > 
 > It should be simple to diagnose since I doubt there is any real
 > AX25 traffic going to these sockets.
 > 
 > Any chance you can figure out what the arguments are that cause
 > this problem?  That'll probably help a lot, thanks!

I've not seen it in a while, I'll have a think about what I can
do to try and provoke it more reliably on Monday.

	Dave

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html