linux-kernel - Re: kobject_set_name() uses GFP

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] [day] [month] [year] [list]

Date:	Wed, 6 May 2009 15:17:52 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kobject_set_name() uses GFP_KERNEL

On Tue, May 5, 2009 at 18:21, Marcel Holtmann <marcel@...tmann.org> wrote:
> all the users of kobject_set_name() which includes dev_set_name() are
> allocating their memory for the device name with GFP_KERNEL. It is not a
> big deal since device_add() does the same. However it is not obvious and
> I ran into an issue in the Bluetooth stack where I was setting the
> device name from a context that can't sleep. If this behavior is on
> purpose, we better add an extra comment in the documentation.

It's the entire driver core and kobjects which use GFP_KERNEL, so it
just "happened" for that function too, I guess.

If it helps to documents that, where should it be added? Maybe you can
just send a patch?

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