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 19:09:04 +0100
From:	Richard Weinberger <richard@....at>
To:	Alexander Holler <holler@...oftware.de>,
	Arend van Spriel <arend@...adcom.com>
CC:	Steven Rostedt <rostedt@...dmis.org>,
	Borislav Petkov <bp@...en8.de>, 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

Am 27.01.2015 um 19:04 schrieb Alexander Holler:
> Am 27.01.2015 um 18:53 schrieb Arend van Spriel:
> 
>> Ever used rgrep or grep -R. Anyway, if this is you use-case what about
>> the gazillion other pieces of info in the kernel. When moving in that
>> direction you can be sure dmesg will flush out.
> 
> Sorry, never heard about that -R and wasn't aware that the kernel does a lot of things. ;)
> 
> I don't want that ftrace stuff appears in dmesg, but I like to do
> 
> dmesg | grep -i mmc (or whatever is of interest)
> 
> instead of
> 
> grep -Rsi mmc /sys/<a hundred tabs to search a matching direcory> or something like
> 
> find /sys -iname '*mmc*' -exec <more silly complications> \;

You don't have to use grep or find.
Add a sysfs attribute, document it in Documentation/ABI and done.
By documenting stuff you'll make the world a better place.

Thanks,
//richard
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ