ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] No more module removal -- Unconference track
Date: Tue, 19 Aug 2014 12:34:58 -0400	[thread overview]
Message-ID: <yq1wqa4v3nx.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20140819160917.GF5423@mwanda> (Dan Carpenter's message of "Tue, 19 Aug 2014 19:09:17 +0300")

>>>>> "Dan" == Dan Carpenter <dan.carpenter@oracle.com> writes:

Dan> If you rmmod a module it probably means that your code was buggy
Dan> before you started the rmmod.  We already taint the kernel when the
Dan> kernel oopses.  It's the same thing.

Buggy does not imply that the rest of the kernel is left in a mangled
state. Also, I load and unload device driver modules many, many times
per day. A significant win on large systems that take half an hour to
boot.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2014-08-19 16:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 14:48 Theodore Ts'o
2014-08-19 14:55 ` Guenter Roeck
2014-08-19 15:23   ` Theodore Ts'o
2014-08-19 15:40     ` Dan Carpenter
2014-08-19 15:47       ` Guenter Roeck
2014-08-19 16:09         ` Dan Carpenter
2014-08-19 16:34           ` Martin K. Petersen [this message]
2014-08-19 16:59           ` Rik van Riel
2014-08-19 17:19           ` Guenter Roeck
2014-08-19 16:43         ` David Woodhouse
2014-08-19 17:13           ` Grant Likely
2014-08-19 17:23             ` David Woodhouse
2014-08-19 15:54     ` Takashi Iwai
2014-08-25 11:01   ` Masami Hiramatsu
2014-08-25 11:05     ` Jiri Kosina
2014-08-26  5:24       ` Masami Hiramatsu
2014-08-27 23:05         ` Theodore Ts'o
2014-08-26 21:39   ` David Howells
2014-08-26 21:45     ` Jiri Kosina
2014-08-27  6:43       ` Masami Hiramatsu

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=yq1wqa4v3nx.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=dan.carpenter@oracle.com \
    --cc=ksummit-discuss@lists.linux-foundation.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