From: Tejun Heo <htejun@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Pedro Francisco <pedrogfrancisco@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ahci rmmodable and shouldn't
Date: Fri, 17 Sep 2010 11:53:19 +0200 [thread overview]
Message-ID: <4C933A8F.2080305@gmail.com> (raw)
In-Reply-To: <47010.148.87.67.141.1284674336.squirrel@www.xenotime.net>
Hello,
On 09/16/2010 11:58 PM, Randy Dunlap wrote:
>> `rmmod ahci' works even if the module is being used (`lsmod' thinks it's
>> not being used but rmmoding ahci triggers filesystem erros and I've to
>> force a reboot).
>>
>> I've been told it's the same as plugging a cable. IMO that's what
>> /sys/stuff/eject_or_similar is to, not `rmmod ahci'.
>>
>>
>> I *assume* it was caused by the split between libahci & ahci, since in
>> 2.6.32
>> `rmmod ahci' is impossible because it's marked as being in use. Didn't try
>> `rmmod -f ahci' but that's not the point.
>>
>>
>> I'm posting again about this because it doesn't make sense to me the
>> actual behaviour.
Just don't rmmod a module which is serving a live filesystem. Why
does it even matter?
--
tejun
next prev parent reply other threads:[~2010-09-17 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 21:56 ahci rmmodable and shouldn't Pedro Francisco
2010-09-16 21:58 ` Randy Dunlap
2010-09-17 9:53 ` Tejun Heo [this message]
2010-09-19 10:28 ` Pedro Francisco
2010-09-19 12:32 ` Tejun Heo
2010-09-20 9:25 ` Pedro Francisco
2010-09-20 9:31 ` Tejun Heo
2010-09-20 9:41 ` Tejun Heo
2010-09-20 20:44 ` Pedro Francisco
2010-09-20 22:09 ` Tejun Heo
2010-09-20 22:10 ` Tejun Heo
2010-09-21 6:14 ` Michael Tokarev
2010-09-21 7:25 ` [PATCH #upstream-fixes] ahci: fix module refcount breakage introduced by libahci split Tejun Heo
2010-09-21 7:32 ` Michael Tokarev
2010-09-21 8:17 ` Tejun Heo
2010-09-23 15:14 ` ahci rmmodable and shouldn't Pedro Francisco
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=4C933A8F.2080305@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pedrogfrancisco@gmail.com \
--cc=rdunlap@xenotime.net \
/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.