linux-kernel - Re: [patch 1/3] bdi patches

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: <3ae72650711300036o92832e3ofa7ea02f7ed83222@mail.gmail.com>
Date:	Fri, 30 Nov 2007 09:36:31 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Miklos Szeredi" <miklos@...redi.hu>
Cc:	neilb@...e.de, a.p.zijlstra@...llo.nl, fengguang.wu@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 1/3] bdi patches

On Nov 30, 2007 9:06 AM, Miklos Szeredi <miklos@...redi.hu> wrote:
> > > Provide a place in sysfs for the backing_dev_info object.
> > > This allows us to see and set the various BDI specific variables.
> >
> > You don't say what the place is, and I'm not quite familiar enough
> > with sysfs internals to figure it out my self.  Help?
>
> /sys/class/bdi  (which sometimes links into /sys/devices/virtual/bdi)
>
> > And while I was looking I noticed that bdi_register (and bdi_init_fmt)
> > takes a second argument 'parent', which is always NULL, and which is
> > undocumented as to purpose.
> > If no-one would ever add another call to bdi_register, why have the
> > second arg, and if they might, how would they know what to put there?

It will get the parent after the block devices are converted from raw
kobjects to core devices. The patch is in Greg's tree.

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