linux-kernel - Re: [PATCH] mmc: print message if a card supports secure erase/trim

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]

Date:	Tue, 27 Jan 2015 13:42:46 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Alexander Holler <holler@...oftware.de>
Cc:	Borislav Petkov <bp@...en8.de>,
	Richard Weinberger <richard@....at>, linux-mmc@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Chris Ball <chris@...ntf.net>,
	Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH] mmc: print message if a card supports secure erase/trim

On Tue, 27 Jan 2015 19:33:52 +0100
Alexander Holler <holler@...oftware.de> wrote:

> Am 27.01.2015 um 19:21 schrieb Steven Rostedt:
> 
> > You want to add a way to tell a property of a device. That is *exactly*
> > what sysfs was made for. Not dmesg.
> 
> Err, dmesg existed long before sysfs.

Yep, and dmesg shows you what is happening in the kernel. sysfs shows
you the state and properties of the kernel (or devices). That's what it
was created for, because dmesg wasn't the place to put it.

> 
> Anyway, it's ok. You're all right and I should request project 
> sponsoring for offering a simple piece of (imho) interesting information.

I'm sure if it's interesting enough, someone will eventually add it.

Hey, if you end up doing it, it could help with your resume.

> 
> Happy frameworking and sorry for disturbing.

No problem. Enjoy,

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