From: Andrea Bittau <a.bittau@cs.ucl.ac.uk>
To: David Miller <davem@redhat.com>
Cc: adobriyan@gmail.com, netdev@vger.kernel.org
Subject: Re: UNIX sockets kernel panic
Date: Thu, 6 Nov 2008 15:14:34 +0000 [thread overview]
Message-ID: <20081106151434.GA4968@shorty> (raw)
In-Reply-To: <20081106.042600.114065285.davem@redhat.com>
I'm still seeing problems with your patch. I'm getting mixed results.
With SMP off, everything seems to work. With SMP, on my laptop, it
still barfs (.26 and .27). Here's a screenshot (literally) of .26:
http://darkircop.org/unix.jpg
I can't seem to reproduce it on qemu using -smp. However, on qemu, with
kernel 2.6.19, your patch, and -smp 2, I can get this one to hang:
http://darkircop.org/unix2.c
On my laptop, with 2.6.19 and SMP on, I think that everything works.
It's likely that it's a scheduling / configuration problem, so I
don't think there's anything magic in .19.
prev parent reply other threads:[~2008-11-06 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 0:14 UNIX sockets kernel panic Andrea Bittau
2008-11-06 1:13 ` Alexey Dobriyan
2008-11-06 1:18 ` David Miller
2008-11-06 12:26 ` David Miller
2008-11-06 15:14 ` Andrea Bittau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081106151434.GA4968@shorty \
--to=a.bittau@cs.ucl.ac.uk \
--cc=adobriyan@gmail.com \
--cc=davem@redhat.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).