| 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
| ||
|
Date: Fri, 13 Dec 2013 16:15:43 -0500 From: Tejun Heo <tj@...nel.org> To: Levente Kurusa <levex@...ux.com> Cc: "Robin H. Johnson" <robbat2@...too.org>, linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org Subject: Re: [PATCH] libata: provide the ability to disable a disk via the params. On Thu, Dec 12, 2013 at 09:36:55PM +0100, Levente Kurusa wrote: > >1. > >Countering your nodisable comment, would it be valid to do: > >libata.force=2:disable libata.force=2.02:nodisable > >To disable all of port 2 except device 2? > > I think that makes sense and I support having 'nodisable'. I really don't want to. Let's please add whatever is necessary for fringe use cases but no more. It's not like this thing is generally useful. > >2. One of my friends wondered if it would be worthwhile to add force > >keywords for other HORKAGE bits, and if so, should the > >ata_lflag/ata_link force bits also be presented? > > I don't think so. Most of the other HORKAGEs are automatically > recognized and applied by the code. I think the only ones > which can cause trouble if not detected at first are the ones that are > currently in the list. Again, just whatever is immediately necessary, please. Thanks. -- tejun -- 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