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] [day] [month] [year] [list]
Date:	Fri, 1 Feb 2013 18:47:29 +0100
From:	Pablo Neira Ayuso <pablo@...filter.org>
To:	Feng Gao <gfree.wind@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Netfilter Development Mailing list 
	<netfilter-devel@...r.kernel.org>
Subject: Re: [ 82/89] netfilter: xt_hashlimit: fix race that results in
 duplicated entries

On Sat, Feb 02, 2013 at 12:56:17AM +0800, Feng Gao wrote:
[...]
> So I wonder How could I commit the patch to kernel directly or how to
> let owner could adopt my fix directly next time?

There is no "file owners" in the Linux kernel, we have subsystem
maintainers that take care of entire source code sub-trees.

You have to send your patches to the corresponding mailing list for
that subsystem. In the specific case of Netfilter, you have to send
your patches to the netfilter-devel mailing list. Make sure your patch
comes with a description and a valid Signed-off-by. If the patch is
not complete, you risk that it passes overlook since patchwork [1]
does not register it.

If your patch is a fix, you can send it anytime. If it is an
enhancement, you have to check if the merge window is open.

The maintainer will get back to you with some ACK/NACK feedback after
some time, if you don't get any, you are free to retry. You can CC
maintainers to attract their attention. You can check the MAINTAINERS
under the linux tree to find the appropriate person.

Regards.

[1] http://patchwork.ozlabs.org/project/netfilter-devel/list/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ