linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Rui Xiang <rui.xiang@huawei.com>,
	containers@lists.linux-foundation.org, serge.hallyn@ubuntu.com,
	linux-kernel@vger.kernel.org, libo.chen@huawei.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH 0/9] Add namespace support for syslog v2
Date: Tue, 30 Jul 2013 08:05:44 +0200	[thread overview]
Message-ID: <20130730080544.3aa38e11@pluto.restena.lu> (raw)
In-Reply-To: <87wqo9urao.fsf@xmission.com>

On Mon, 29 Jul 2013 11:58:23 -0700 Eric W. Biederman wrote:
> Rui Xiang <rui.xiang@huawei.com> writes:
> 
> > This patchset introduces a system log namespace.
> 
> The largest outstanding question is not answered.  Can't we just fix
> iptables to log somehwere better than dmesg, and would that not entirely
> remove the need for this work?

Doesn't NFLOG target + ulogd allow for this?

Though last I tried it seems the corresponding netlink resources are not
(fully) netns aware (unless I did something wrong in my setup).

Bruno


> That question needs to be answered before we proceed down this path.
> 
> Eric

      parent reply	other threads:[~2013-07-30  6:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  2:31 [PATCH 0/9] Add namespace support for syslog v2 Rui Xiang
2013-07-29  2:31 ` [PATCH 1/9] syslog_ns: add syslog_namespace and put/get_syslog_ns Rui Xiang
2013-07-29  9:40   ` Gu Zheng
2013-07-29 11:47     ` Rui Xiang
2013-07-30  0:46       ` Gu Zheng
2013-07-29  2:31 ` [PATCH 2/9] syslog_ns: add syslog_ns into user_namespace Rui Xiang
2013-07-29  9:46   ` Gu Zheng
2013-07-29  9:54     ` Gao feng
2013-07-29  9:56       ` Gu Zheng
2013-07-29  2:31 ` [PATCH 3/9] syslog_ns: add init syslog_ns for global syslog Rui Xiang
2013-07-29  2:31 ` [PATCH 4/9] syslog_ns: make syslog handling per namespace Rui Xiang
2013-07-29  9:50   ` Gu Zheng
2013-08-01  1:36   ` Gao feng
2013-08-01  3:10     ` Rui Xiang
2013-08-01  5:38       ` Gao feng
2013-08-01  6:29         ` Rui Xiang
2013-07-29  2:31 ` [PATCH 5/9] syslog_ns: make permisiion check per user namespace Rui Xiang
2013-07-29  2:31 ` [PATCH 6/9] syslog_ns: use init syslog_ns for console action Rui Xiang
2013-07-29  2:31 ` [PATCH 7/9] syslog_ns: implement function for creating syslog ns Rui Xiang
2013-07-29 10:25   ` Gu Zheng
2013-07-30  3:39     ` Rui Xiang
2013-07-30  3:42       ` Gu Zheng
2013-07-29 10:39   ` Gao feng
2013-07-29  2:31 ` [PATCH 8/9] syslog_ns: implement ns_printk for specific syslog_ns Rui Xiang
2013-07-29 10:37   ` Gu Zheng
2013-07-29 12:17     ` Rui Xiang
2013-07-29  2:31 ` [PATCH 9/9] netfilter: use ns_printk in iptable context Rui Xiang
2013-07-29  9:48   ` Gao feng
2013-07-29 12:37     ` Rui Xiang
2013-07-29  9:33 ` [PATCH 0/9] Add namespace support for syslog v2 Gu Zheng
2013-07-29 18:58 ` Eric W. Biederman
2013-07-30  2:11   ` Rui Xiang
2013-07-30  6:05   ` Bruno Prémont [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=20130730080544.3aa38e11@pluto.restena.lu \
    --to=bonbons@linux-vserver.org \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=libo.chen@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.xiang@huawei.com \
    --cc=serge.hallyn@ubuntu.com \
    /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).