From: Jarek Poplawski <jarkao2@gmail.com>
To: "Bernard, f6bvp" <f6bvp@free.fr>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
Ralf Baechle DL5RB <ralf@linux-mips.org>
Subject: Re: ax25 rose Re: kernel panic linux-2.6.27-rc7
Date: Thu, 2 Oct 2008 21:48:45 +0200 [thread overview]
Message-ID: <20081002194845.GB2664@ami.dom.local> (raw)
In-Reply-To: <1222971618.6267.26.camel@f6bvp-5>
On Thu, Oct 02, 2008 at 08:20:18PM +0200, Bernard, f6bvp wrote:
> Hi Jarek,
Hi Bernard,
>
> Finally I am able to access the faulty 2.6.27-rc7 f6bvp-9 system via
> ssh.
> I can read /var/log/kernel/message file immediately after a kernel
> failure and a reboot.
> When this is done, the system is stable until I start FPAC suite
> applications (fpad, fpacwpd ...) as shown below.
>
> Oct 2 16:50:00 f6bvp-9 kernel: AX25_DBG: c36fc338, 00000000, 1, 0, 0
...
This looks like the output from debugging patch #1 and I'm now more
interested with #2 (which I resend below). I also append a new patch
here (let's call this #4) to netrom. So try to use 2.6.27-rc with
these patches only:
- debugging patch #2 (net/core/sock.c)
- patch #3 (drivers/net/lib8390.c)
- patch #4 (net/netrom/af_netrom.c)
> Although I did not change anything, and contrarily to my previous
> observation, the system instability as shown above occurs
> systematically.
> There was no problem with Kernel 2.6.25-10 I was using before (with
> patches for AX25 and ROSE that are now included in 2.6.27-rc7).
> I did not try 2.6.26 on this machine, thus I cannot tell if the bug was
> already present.
> Would it be worth to test 2.6.26 ?
Yes, but only if you think you can do it safely.
> With the SSH limited access I have from my remote site, can I continue
> this debuging effort constructively, or do we wait until I am back in
> front of the local console ?
This debugging can still oops, so it depends on you. I need some warning
log from this debugging patch #2, so if you are sure this could safely
reboot to some default kernel? Otherwise I can wait, no problem.
Cheers,
Jarek P.
--- (debugging patch #2)
net/core/sock.c | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/net/core/sock.c b/net/core/sock.c
index 2d358dd..3ad8eaa 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -960,6 +960,15 @@ void sk_free(struct sock *sk)
{
struct sk_filter *filter;
+ if (sk->sk_socket) {
+ printk("AX25_DBG: %p, %p, %u, %u, %u, %p\n", sk, sk->sk_socket,
+ sk->sk_family, sk->sk_type, sk->sk_protocol, sk->sk_socket->sk);
+ if (sk->sk_family == 3 && sk->sk_type == 5 && sk->sk_protocol == 240) {
+ WARN_ON_ONCE(1);
+ sock_orphan(sk);
+ }
+ }
+
if (sk->sk_destruct)
sk->sk_destruct(sk);
--- (patch #4)
net/netrom/af_netrom.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/netrom/af_netrom.c b/net/netrom/af_netrom.c
index 532e4fa..9f1ea4a 100644
--- a/net/netrom/af_netrom.c
+++ b/net/netrom/af_netrom.c
@@ -525,6 +525,7 @@ static int nr_release(struct socket *sock)
if (sk == NULL) return 0;
sock_hold(sk);
+ sock_orphan(sk);
lock_sock(sk);
nr = nr_sk(sk);
@@ -548,7 +549,6 @@ static int nr_release(struct socket *sock)
sk->sk_state = TCP_CLOSE;
sk->sk_shutdown |= SEND_SHUTDOWN;
sk->sk_state_change(sk);
- sock_orphan(sk);
sock_set_flag(sk, SOCK_DESTROY);
break;
next prev parent reply other threads:[~2008-10-02 19:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 12:49 kernel panic linux-2.6.27-rc7 Bernard Pidoux F6BVP
2008-09-29 12:30 ` ax25 rose " Jarek Poplawski
2008-09-30 9:40 ` Bernard Pidoux F6BVP
2008-09-30 10:10 ` Jarek Poplawski
2008-09-30 11:17 ` Jarek Poplawski
2008-09-30 20:59 ` Bernard Pidoux F6BVP
2008-09-30 21:30 ` Jarek Poplawski
2008-09-30 22:49 ` Bernard Pidoux F6BVP
2008-10-01 5:58 ` Jarek Poplawski
2008-10-02 18:20 ` Bernard, f6bvp
2008-10-02 19:48 ` Jarek Poplawski [this message]
2008-10-03 7:34 ` Jarek Poplawski
2008-10-03 7:43 ` Jarek Poplawski
2008-10-04 18:30 ` Bernard, f6bvp
2008-10-04 19:11 ` Jarek Poplawski
2008-10-04 20:09 ` Jarek Poplawski
2008-10-05 15:40 ` Bernard, f6bvp
2008-10-05 20:33 ` Jarek Poplawski
2008-10-05 21:09 ` Jarek Poplawski
2008-10-05 18:31 ` Bernard, f6bvp
2008-10-05 20:40 ` Jarek Poplawski
2008-10-05 21:18 ` Bernard, f6bvp
2008-10-05 22:05 ` [PATCH to REVERT] " Jarek Poplawski
2008-10-06 20:05 ` David Miller
2008-10-05 22:16 ` [PATCH] netrom: Fix sock_orphan() use in nr_release Jarek Poplawski
2008-10-05 13:04 ` ax25 rose Re: kernel panic linux-2.6.27-rc7 Jarek Poplawski
2008-10-01 6:58 ` [PATCH] lib8390: Fix locking in ei_poll (poll controller) Jarek Poplawski
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=20081002194845.GB2664@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=f6bvp@free.fr \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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).