linux-kernel - Re: [PATCH 3/3] bdi: Initialize noop_backing_dev

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: <20100727171729.GD6820@quack.suse.cz>
Date:	Tue, 27 Jul 2010 19:17:30 +0200
From:	Jan Kara <jack@...e.cz>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Jan Kara <jack@...e.cz>, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 3/3] bdi: Initialize noop_backing_dev_info properly

On Tue 27-07-10 13:09:39, Christoph Hellwig wrote:
> On Tue, Jul 27, 2010 at 07:05:01PM +0200, Jan Kara wrote:
> > Properly initialize this backing dev info so that writeback code does not
> > barf when getting to it e.g. via sb->s_bdi.
> 
> When do we actually get it in s_bdi?  That should never happen.
  Well, set_anon_super() sets it. I'm not sure if filesystems using this
are supposed to reset it to something else or not... It's a bit messy and
nowhere is actually written how things should be. One can just guess ;)


								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/