linux-kernel - Re: Checking module parameters

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 17 Jan 2009 18:22:11 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	David Wagner <daw@...berkeley.edu>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Checking module parameters

David Wagner wrote:
> Is there a way to tell what options have been applied to a currently
> loaded kernel module?
> 
> I'm trying to force libata to use 1.5Gbps rather than 3Gbps, so I created
> a file /etc/modprobe.d/local containing:
>   options libata force=1.5Gbps
> However my SATA drive gets loaded at 3Gbps.  I'm trying to figure out how
> to debug this so that I can tell whether the option got correctly applied
> to the libata module, and if not, how to force the SATA link to 1.5Gbps.
> Any suggestions or ideas?
> 
> (I can't set libata.force=1.5Gbps as a kernel argument because on my
> Fedora kernel, libata is loaded as a module rather than built into the
> kernel.  I can't run "modprobe libata force=1.5Gbps" by hand because
> I've got SATA drives, so the libata module is automatically loaded before
> I get shell access.)

Rebuilding the initrd with that option set should cause the initrd to 
pass the option into the libata module when the initrd script loads it. 
Unfortunately the current Fedora mkinitrd is broken such that this 
doesn't work. I'm rather disappointed by the lack of response to this 
bug as it seems like it should be easily resolved and causes serious 
problems with debugging certain issues, as you've found. Anyone know who 
needs to be hit with a clue-by-four to get this fixed?

https://bugzilla.redhat.com/show_bug.cgi?id=457870
--
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/