From: Cong Wang <amwang@redhat.com>
To: Helge Deller <deller@gmx.de>
Cc: Octavian Purdila <opurdila@ixiacom.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Frank Danapfel <fdanapfe@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
Linus <torvalds@linux-foundation.org>
Subject: Re: [PATCH] enhance usability of /proc/sys/net/ipv4/ip_local_reserved_ports
Date: Mon, 12 Mar 2012 11:42:39 +0800 [thread overview]
Message-ID: <1331523759.1932.13.camel@cr0> (raw)
In-Reply-To: <4F5BE563.9050506@gmx.de>
Hello, Helge,
On Sun, 2012-03-11 at 00:36 +0100, Helge Deller wrote:
> When writing to the ip_local_reserved_ports proc file it will currently clear
> all previously reserved ports and update the current list with the one given
> in the input.
>
> This behaviour makes it's usage quite hard, for example:
> a) The generic proc filesystem limitation of only handle up to PAGE_SIZE-1
> characters at maximum may not be sufficient to provide all your wished-to-
> be-reserved ports at once.
Yes, this should be extended IMHO.
> b) There is no easy way to disable specific given ports, you always need to
> give the full port list at once. This makes shell scripting hard, since
> you need to parse everything yourself.
> c) There is no easy way to just add specific ports or port ranges. Again,
> this would be useful for shell scripts.
>
These could be calculated in user-space, although it maybe not as easy
as you want.
> The following patch solves this problem by simply extending the parser
> in proc_do_large_bitmap() to accept the keywords "add" and "release" in front
> of given ports or port ranges and to either add or drop the given ports
> from the already existing list.
This looks a little odd, because we do "magic" things with a sysctl
file, which is supposed to be plain text file. Do we have existing
examples?
BTW, as David mentioned, please Cc netdev next time.
Thanks.
next prev parent reply other threads:[~2012-03-12 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 23:36 [PATCH] enhance usability of /proc/sys/net/ipv4/ip_local_reserved_ports Helge Deller
2012-03-11 22:55 ` David Miller
2012-03-12 3:42 ` Cong Wang [this message]
2012-03-12 21:09 ` Helge Deller
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=1331523759.1932.13.camel@cr0 \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=ebiederm@xmission.com \
--cc=fdanapfe@redhat.com \
--cc=lersek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=torvalds@linux-foundation.org \
/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).