linux-kernel - Re: linux-next: build warninga in Linus' tree

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: <20110603111048.GR12709@twin.jikos.cz>
Date:	Fri, 3 Jun 2011 13:10:49 +0200
From:	David Sterba <dave@...os.cz>
To:	Mitch Harder <mitch.harder@...ayonlinux.org>
Cc:	dave@...os.cz, Stephen Rothwell <sfr@...b.auug.org.au>,
	Chris Mason <chris.mason@...cle.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-btrfs@...r.kernel.org, kreijack@...ero.it
Subject: Re: linux-next: build warninga in Linus' tree

On Wed, Jun 01, 2011 at 10:16:48AM -0500, Mitch Harder wrote:
> I've been playing around with resurrecting the basic sysfs
> capabilities that had been previously incorporated into btrfs.
> 
> As it stands right now, it was relatively easy to re-implement sysfs
> as it was originally.  However, that implementation of sysfs wasn't
> populated with much information (only total_blocks, blocks_used, and
> blocksize).

Goffredo Baroncelli (CCed) posted a patch to enhance sysfs interface:

https://patchwork.kernel.org/patch/308902/
(http://www.spinics.net/lists/linux-btrfs/msg06777.html)

> I also had to reverse a small portion of code that was in the last
> clean-up.

Restoring the code should not be a problem, the cleanup was too eager
and I think a sysfs inteface would be good, not only for debugging
purposes or tuning.

> If a CONFIG_BTRFS_DEBUG type configuration flag is ever introduced, it
> would be interesting to resurrect btrfs' sysfs capabilities.

Hearing about CONFIG_BTRFS_DEBUG again, seems worth to add it.


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