linux-kernel - Re: May the worker function free its struct

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: <20100510045252.GC3387@windriver.com>
Date:	Mon, 10 May 2010 12:52:52 +0800
From:	Yong Zhang <yong.zhang@...driver.com>
To:	Leon Woestenberg <leon.woestenberg@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: May the worker function free its struct_work (plus container)?

On Mon, May 10, 2010 at 12:47:23AM +0200, Leon Woestenberg wrote:
> Hello,
> 
> may the worker function kfree() it's own work data structure?

Actually, workqueue has no restriction on this kind of operation.
But if you must be careful with the caller in case it will refer
the freed struct.

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