From: Jon Masters <jonathan@jonmasters.org>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Patrick McHardy <kaber@trash.net>,
adam@yggdrasil.com, jcm@jonmasters.org,
netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix (improve) deadlock condition on module removal netfilter socket option removal
Date: Wed, 05 Sep 2007 17:39:11 -0400 [thread overview]
Message-ID: <1189028351.12261.166.camel@jcmlaptop> (raw)
In-Reply-To: <20070905192744.GB25050@hmsreliant.think-freely.org>
On Wed, 2007-09-05 at 15:27 -0400, Neil Horman wrote:
> Now, I suppose its possible that I've not been looking at the right source tree
> when doing my work. I've based my modprobe patch on this git tree:
> http://git.kernel.org/?p=linux/kernel/git/kyle/module-init-tools.git;a=summary
> If theres a newer one, if you could please point it out to me, I'd appreciate
> it. If the functional equivalent of my second patch is already in there, then
> we just need my first patch to be good to go.
Neil, please test:
http://www.kernel.org/pub/linux/kernel/people/jcm/module-init-tools/module-init-tools-3.3-pre12.tar.bz2
Jon.
next prev parent reply other threads:[~2007-09-05 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 20:24 [PATCH 0/2] Fix (improve) deadlock condition on module removal netfilter socket option removal Neil Horman
2007-09-05 15:22 ` Patrick McHardy
2007-09-05 16:13 ` Rusty Russell
2007-09-05 17:08 ` Neil Horman
2007-09-05 17:41 ` Rusty Russell
2007-09-05 18:19 ` Jon Masters
2007-09-05 19:27 ` Neil Horman
2007-09-05 20:17 ` Jon Masters
2007-09-05 20:51 ` Rusty Russell
2007-09-05 20:59 ` Jon Masters
2007-09-05 21:39 ` Jon Masters [this message]
2007-09-06 0:17 ` Neil Horman
2007-09-06 12:55 ` Neil Horman
2007-09-06 13:35 ` Jon Masters
2007-09-06 15:40 ` Neil Horman
2007-09-06 10:33 ` Patrick McHardy
2007-09-06 11:08 ` Neil Horman
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=1189028351.12261.166.camel@jcmlaptop \
--to=jonathan@jonmasters.org \
--cc=adam@yggdrasil.com \
--cc=jcm@jonmasters.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=nhorman@tuxdriver.com \
--cc=rusty@rustcorp.com.au \
/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.