lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45732C8E.4060801@wpkg.org>
Date:	Sun, 03 Dec 2006 20:59:10 +0100
From:	Tomasz Chmielewski <mangoo@...g.org>
To:	Ross Vandegrift <ross@...listi.us>
Cc:	Andreas Schwab <schwab@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: why can't I remove a kernel module (or: what uses a given module)?

Ross Vandegrift wrote:
> On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
>> You mean the "Used by" column? No, it's not used by any other module 
>> according to lsmod output.
>>
>> Any other methods of checking what uses /dev/sda*?
> 
> There's a good chance that if it was loaded at system boot, hald or
> udev may be doing something with it.

This machine doesn't have hal; when I kill udevd still doesn't help.

Yes, something's using that drive, be it a program, a module (unlikely), 
or something that is compiled directly in the kernel (for example, 
md/raid1).
But what is it?

Kernel knows it, as it refuses to remove the module (via rmmod), but how 
to tell kernel to share this knowledge with me?


-- 
Tomasz Chmielewski
http://wpkg.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ