All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Bernard" <seb@frankengul.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] fix iptables on systems with discontiguous processor ids
Date: Wed, 12 Oct 2005 09:04:13 +0200	[thread overview]
Message-ID: <434CB56D.7050508@frankengul.org> (raw)
In-Reply-To: <20051011.233149.40160652.davem@davemloft.net>

David S. Miller a écrit :

>From: seb@frankengul.org
>Date: Wed, 12 Oct 2005 08:22:18 +0200
>
>  
>
>>After building, the modules_install reports the symbol undefined.
>>Well, I see now that it is only a lack of EXPORT_SYMBOL.
>>    
>>
>
>Aha, that makes sense.
>
>  
>
>>All smp arch used cpu_online_map and cpu_possible_map but sparc which
>>used phys_cpu_present_map (a specificity of the sparc port I presume).
>>    
>>
>
>Yes, we do this because since we lack cpu hotplug support
>this means "cpu present"=="cpu possible".
>
>  
>
Ok, heres is the oops provoked by the second patch posted by Harald on 
the 11th of October.

unable to handle paging_request (some zeros...)140098000

iptables_restor(2488): Oops [#1]
TPC: <get_couters +0x68/0xe0>

Caller: do_ipt_get_ctl + 0x5b8/0x7a0
            nf_sock_opt + 0xa4 / 0x160
            ip_get_sockopt + 0xa4 / 0x5e0
            sock_common_getsockopt + 0x1c/0x40
            sys_get_sockopt + 0x84/0xe0
            compat_sys_getsockopt + 0x28/0x120
            linux_sparc_syscall32 + 0x34/0x40

Note that it is a different crash.
The previous was a unable to handle kernel request NULL dereference.
As a result, the machine locks hard.

Hope it helps.

    Seb

  reply	other threads:[~2005-10-12  7:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-10 16:41 [PATCH] fix iptables on systems with discontiguous processor ids Harald Welte
2005-10-10 21:15 ` David S. Miller
2005-10-10 21:41   ` Patrick McHardy
2005-10-10 21:52     ` Patrick McHardy
2005-10-10 22:06       ` David S. Miller
2005-10-11 14:23         ` Harald Welte
2005-10-11 19:39           ` David S. Miller
2005-10-12  6:36             ` Harald Welte
2005-10-10 22:04     ` David S. Miller
2005-10-10 21:46   ` Harald Welte
2005-10-11 13:54     ` Henrik Nordstrom
2005-10-11 14:13       ` Eric Dumazet
2005-10-11 17:45         ` Harald Welte
2005-10-11 22:57           ` David S. Miller
2005-10-12  7:00             ` Harald Welte
2005-10-13 22:01             ` Eric Dumazet
2005-10-17  4:18               ` David S. Miller
2005-10-11 10:44   ` Harald Welte
2005-10-11 17:15     ` Bart De Schuymer
2005-10-11 17:55       ` Harald Welte
2005-10-11 17:54     ` Harald Welte
2005-10-11 21:54       ` Sébastien Bernard
2005-10-11 22:32         ` David S. Miller
2005-10-12  6:22           ` seb
2005-10-12  6:31             ` David S. Miller
2005-10-12  7:04               ` Sébastien Bernard [this message]
2005-10-12  7:34                 ` David S. Miller
2005-10-12  6:43         ` Harald Welte
2005-10-12 22:54       ` David S. Miller
2005-10-13  7:18         ` seb
2005-10-13 19:11           ` David S. Miller
2005-10-13  8:46         ` Herbert Xu
2005-10-13 21:14           ` David S. Miller
2005-10-13 22:37             ` seb
2005-10-14 18:33             ` Harald Welte
2005-10-10 21:48 ` Sébastien Bernard
2005-10-11 14:23   ` Harald Welte
2005-10-11 20:59     ` Sébastien Bernard
2005-10-11 21:33       ` David S. Miller
2005-10-12  6:40       ` Harald Welte

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=434CB56D.7050508@frankengul.org \
    --to=seb@frankengul.org \
    --cc=davem@davemloft.net \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.