From: Jeremy Kerr <jk@ozlabs.org>
To: linuxppc-dev@ozlabs.org
Subject: Re: PATCH: free mm if spufs_fill_dir() failed
Date: Wed, 9 May 2007 16:08:26 +1000 [thread overview]
Message-ID: <200705091608.26934.jk@ozlabs.org> (raw)
In-Reply-To: <463B6D16.9050400@linux.vnet.ibm.com>
Sebastian,
> In case spufs_fill_dir() fails only put_spu_context()
> gets called for cleanup and the acquired mm_struct never gets freed.
Good catch. However - could we do the mmput in the context destroy path
instead?
Also, you're probably better-off sending patches inline. It makes
commenting on the patch much easier for some mailers.
Cheers,
Jeremy
prev parent reply other threads:[~2007-05-09 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 17:27 PATCH: free mm if spufs_fill_dir() failed Sebastian Siewior
2007-05-09 6:08 ` Jeremy Kerr [this message]
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=200705091608.26934.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.