netdev - [PATCH v3] Merge ipt_LOG and ip6t_LOG, add ring bufffer support

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-next>] [day] [month] [year] [list]

Date:	Sun,  5 Feb 2012 01:14:46 +0100
From:	Richard Weinberger <richard@....at>
To:	netfilter-devel@...r.kernel.org
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	eric.dumazet@...il.com, jengelh@...ozas.de, rostedt@...dmis.org
Subject: [PATCH v3] Merge ipt_LOG and ip6t_LOG, add ring bufffer support

This patch set merges ipt_LOG and ip6t_LOG and adds ring buffer support
to xt_LOG.

Using "--ring" an user can create LOG rules which log messages into
one or more ring buffers.
Each ring buffer is represented as pipe-like file in
/proc/net/netfilter/xt_LOG_ring/.

Ring buffer support can be enabled/disabled using
CONFIG_NETFILTER_XT_TARGET_LOG_RING.

Changes since v1:
 - Merged ipt_LOG and ip6t_LOG
 - Implemented ring buffer support as part of xt_LOG.

Changes since v2:
 - Fixed struct xt_log_info_v1's data layout
 - Removed the sizeof(void *) hack
 - Replaced BUG() by WARN_ON_ONCE()


git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc.git xt_LOG
[PATCH 1/4] Netfilter: Merge ipt_LOG and ip6_LOG into xt_LOG
[PATCH 2/4] ring_buffer: Export for_each_buffer_cpu()
[PATCH 3/4] xt_log: Make printk() in sb_close() optional
[PATCH 4/4] Netfilter: xt_LOG: Implement ring buffer support

git://git.kernel.org/pub/scm/linux/kernel/git/rw/iptables.git xt_LOG
[PATCH 1/2] iptables: Merge libip6t_LOG and libipt_LOG into libxt_LOG
[PATCH 2/2] iptables: xt_LOG: Add ring buffer support

Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html