linux-kernel - Re: [PATCH] mmc : export hw reset function info to user

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: <108743536.474964.1316449188347.JavaMail.root@zimbra-prod-mbox-2.vmware.com>
Date:	Mon, 19 Sep 2011 09:19:48 -0700 (PDT)
From:	Andrei Warkentin <awarkentin@...are.com>
To:	Namjae Jeon <linkinjeon@...il.com>
Cc:	linux-kernel@...r.kernel.org, cjb@...top.org,
	linux-mmc@...r.kernel.org
Subject: Re: [PATCH] mmc : export hw reset function info to user

Hi Namjae, others,

----- Original Message -----
> From: "Namjae Jeon" <linkinjeon@...il.com>
> To: cjb@...top.org, linux-mmc@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org, "Namjae Jeon" <linkinjeon@...il.com>
> Sent: Sunday, September 18, 2011 11:20:25 AM
> Subject: [PATCH] mmc : export hw reset function info to user
> 
> user app should know whether hw reset function is enable to use it.
> so I try to add sysfs file of hw reset function like enhanced area.
> 

If we're going to be adding a bunch of attributes from ext_csd, why not
just allow dumping the entire ext_csd in a semi-readable form? Via something like 
hex_dump_to_buffer. This will allow easy human an machine parsing, and be more 
lightweight then adding a sysfs attr for each EXT_CSD byte (of which there are a lot).

I'm basing this on the thought that the only clients of these attrbutes would
either be developers or engineers involved with MMC media, or very specialized
software.

Thoughts?

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