linux-kernel - 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-next>] [day] [month] [year] [list]

Message-Id: <200901172226.n0HMQEEJ024690@taverner.cs.berkeley.edu>
Date:	Sat, 17 Jan 2009 14:26:14 -0800 (PST)
From:	David Wagner <daw@...berkeley.edu>
To:	linux-kernel@...r.kernel.org
Subject: Checking module parameters

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.)
--
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/