linux-kernel - libata: can't set force= on subdevice

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

Message-ID: <20130405045628.GA27991@foursquare.net>
Date:	Fri, 5 Apr 2013 00:56:28 -0400
From:	Chris Frey <cdfrey@...rsquare.net>
To:	linux-kernel@...r.kernel.org
Subject: libata: can't set force= on subdevice

Hi,

Using kernel 3.2.x (Debian Wheezy) and when setting libata.force= kernel
command line parameters, there seems to be a conflict with the '.'.

For example, with the following boot argument:

	libata.force=ata1.0:udma/44

I get:

	libata: Unknown parameter '0:udma/44'
	libata: Unknown parameter '0:udma/44'
	libata: Unknown parameter '0:udma/44'
	libata: Unknown parameter '0:udma/44'

Which I think is from kernel/params.c, not drivers/ata/libata-core.c.

- Chris

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