linux-kernel - Re: Asynchronous scsi scanning

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]

Message-ID: <adabqglo4mc.fsf@cisco.com>
Date:	Tue, 15 May 2007 19:59:39 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Satyam Sharma <satyam.sharma@...il.com>,
	Simon Arlott <simon@...e.lp0.eu>,
	James Bottomley <james.bottomley@...eleye.com>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org, kernel-packagers@...r.kernel.org,
	"Robert P. J. Day" <rpjday@...dspring.com>
Subject: Re: Asynchronous scsi scanning

 > No, it does matter.  Your suggestion doesn't work, because
 > /sys/module/scsi_mod/parameters/ belongs to the module code.  To create
 > a new attribute there, you use the module_param() code -- and there's
 > no way to have code called when your parameter is changed.

If I'm not misunderstanding what you're talking about, there is
actually a way to have code called when a module parameter is changed:
module_param_call().

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