From: Jeff Moyer <jmoyer@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
autofs mailing list <autofs@linux.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] autofs4 - add missing kfree
Date: Fri, 20 Jun 2008 09:02:32 -0400 [thread overview]
Message-ID: <x49ej6stg2f.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20080620070923.17224.33149.stgit@raven.themaw.net> (Ian Kent's message of "Fri, 20 Jun 2008 15:09:25 +0800")
Ian Kent <raven@themaw.net> writes:
> It see that the patch tittled "autofs4 - fix pending mount race" is
> missing a change that I had recently made.
>
> It's missing a kfree for the case mutex_lock_interruptible() fails
> to aquire the wait queue mutex.
Yeah, missed that in the translation to the embedded qstr.
> Ian
>
> Signed-off-by: Ian Kent <raven@themaw.net>
Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
prev parent reply other threads:[~2008-06-20 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 7:09 [PATCH] autofs4 - add missing kfree Ian Kent
2008-06-20 13:02 ` Jeff Moyer [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=x49ej6stg2f.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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;
as well as URLs for NNTP newsgroup(s).