From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, lyw@cn.fujitsu.com
Subject: Re: [Bugme-new] [Bug 16268] New: kernel oops when rmmod the tcp_diag modules
Date: Wed, 23 Jun 2010 00:02:42 +0200 [thread overview]
Message-ID: <1277244162.2591.198.camel@edumazet-laptop> (raw)
In-Reply-To: <20100622141232.4b8f1d4a.akpm@linux-foundation.org>
Le mardi 22 juin 2010 à 14:12 -0700, Andrew Morton a écrit :
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 22 Jun 2010 00:43:37 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=16268
> >
> > Summary: kernel oops when rmmod the tcp_diag modules
> > Product: Networking
> > Version: 2.5
> > Kernel Version: 2.6.35-rc3
> > Platform: All
> > OS/Version: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: high
> > Priority: P1
> > Component: IPV4
> > AssignedTo: shemminger@linux-foundation.org
> > ReportedBy: lyw@cn.fujitsu.com
> > Regression: No
> >
> >
> > I found a crash problem use following scripts and steps
> >
> > #cat run_ss.sh
> > while [ 1 ]
> > do
> > ss -a
> > done
> >
> > #cat rmmod.sh
> > while [ 1 ]
> > do
> > rmmod -f tcp_diag >/dev/null 2>&1
> > rmmod -f inet_diag >/dev/null 2>&1
> > done
> >
> > step1:
> > # sh run_sh.sh
> > step2:
> > # sh rmmod.sh
>
> I assume the rmmod script runs in pararallel with run_ss.sh.
>
> What is "ss"? Something which triggers a load of kernel modules,
> presumably. Which ones?
>
ss is kind of "netstat" with advanced features.
It loads inet_diag & tcp_diag modules.
> > After step2, the kernel oopsed.
>
> yeah, that was a pretty nasty test ;)
Well, they are faster and more predictable ways to reboot a machine, if
you ask me :)
man rmmod
-f --force
This option can be extremely dangerous: it has no effect unless
CONFIG_MODULE_FORCE_UNLOAD was set when the kernel was compiled.
With this option, you can remove modules which are being used,
or which are not designed to be removed, or have been marked as
unsafe (see lsmod(8)).
I guess Linux is supposed to respect admin choice to live in a dangerous world.
next prev parent reply other threads:[~2010-06-22 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16268-10286@https.bugzilla.kernel.org/>
2010-06-22 21:12 ` [Bugme-new] [Bug 16268] New: kernel oops when rmmod the tcp_diag modules Andrew Morton
2010-06-22 21:21 ` David Miller
2010-06-22 22:02 ` Eric Dumazet [this message]
2010-06-22 22:25 ` Andrew Morton
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=1277244162.2591.198.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=lyw@cn.fujitsu.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