public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yong Zhang <yong.zhang@windriver.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: May the worker function free its struct_work (plus container)?
Date: Mon, 10 May 2010 12:52:52 +0800	[thread overview]
Message-ID: <20100510045252.GC3387@windriver.com> (raw)
In-Reply-To: <AANLkTikTPkLID3e8HpT1jMeiF9tQ6-7oJWQBfiRF7xUN@mail.gmail.com>

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

  reply	other threads:[~2010-05-10  4:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09 22:47 May the worker function free its struct_work (plus container)? Leon Woestenberg
2010-05-10  4:52 ` Yong Zhang [this message]
2010-05-10 10:18   ` Leon Woestenberg
2010-05-11  1:27     ` Yong Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100510045252.GC3387@windriver.com \
    --to=yong.zhang@windriver.com \
    --cc=leon.woestenberg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox