Messages in this thread | | | Date | Fri, 15 Nov 2002 17:00:30 -0800 (PST) | From | "Randy.Dunlap" <> | Subject | Re: Reserving "special" port numbers in the kernel ? |
| |
On 15 Nov 2002, Arun Sharma wrote:
| xavier.bestel@free.fr (Xavier Bestel) writes: | | > Le sam 16/11/2002 à 01:00, Arun Sharma a écrit : | > > One of the Intel server platforms has a magic port number (623) that | > > it uses for remote server management. However, neither the kernel nor | > > glibc are aware of this special port. | > > | > > As a result, when someone requests a privileged port using | > > bindresvport(3), they may get this port back and bad things happen. | > > | > > Has anyone run into this or similar problems before ? Thoughts on | > > what's the right place to handle this issue ? | > | > run a dummy app at startup which reserves that port ? | | Yes, I'm already aware of this one, but was looking for a lighter weight | solution (ideally a config file change) that doesn't involve running an | extra process (think of doing this on a large number of machines).
Look in arch/i386/kernel/setup.c (in 2.4.19):
There is this array: struct resource standard_io_resources[] = ... that you could add to; you could even make the addition a CONFIG_ option.
-- ~Randy "I read part of it all the way through." -- Samuel Goldwyn
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |