From: Valdis.Kletnieks@vt.edu
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
ML netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [next] unix stream crashes
Date: Fri, 02 Sep 2011 12:12:16 -0400 [thread overview]
Message-ID: <6805.1314979936@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 01 Sep 2011 18:40:45 PDT." <1314927645.2576.2939.camel@schen9-DESK>
[-- Attachment #1.1: Type: text/plain, Size: 750 bytes --]
On Thu, 01 Sep 2011 18:40:45 PDT, Tim Chen said:
> 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.
Dell Latitude E6500, Core2 T8700 processor, x86_64 kernel, a slightly mangled
Fedora Rawhide userspace. I'd not be surprised if there's an idiocyncratic
setting in my .config that makes the bug crawl out of the woodwork on my box,
so I'm attaching the .config in case it provides some enlightenment.
If you want me to try a debugging or test patch, let me know...
[-- Attachment #1.2: config.gz --]
[-- Type: application/x-gzip , Size: 18974 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-09-02 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 20:46 Jiri Slaby
2011-09-02 0:49 ` Valdis.Kletnieks
2011-09-02 1:40 ` Tim Chen
2011-09-02 16:12 ` Valdis.Kletnieks [this message]
2011-09-02 23:55 ` Tim Chen
2011-09-03 4:32 ` Sedat Dilek
2011-09-03 5:35 ` Valdis.Kletnieks
2011-09-03 5:54 ` Sedat Dilek
2011-09-03 6:23 ` Jiri Slaby
2011-09-03 12:30 ` Yan, Zheng
2011-09-03 13:47 ` Sedat Dilek
2011-09-03 14:46 ` Sedat Dilek
2011-09-03 15:38 ` Yan, Zheng
2011-09-04 14:43 ` Valdis.Kletnieks
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=6805.1314979936@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=davem@davemloft.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tim.c.chen@linux.intel.com \
/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
all inboxes | Powered by JetHome®