diff options
| author | Chris Novakovic <chris@chrisn.me.uk> | 2018-04-24 04:56:35 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-04-24 19:40:41 +0200 |
| commit | de1fa15b6642f0b66f1844b9b464a8c28e84347c (patch) | |
| tree | dffa5c3adf8ca466eb5e9fdea8a7016cabf50c47 /mm/page_io.c | |
| parent | ipconfig: BOOTP: Don't request IEN-116 name servers (diff) | |
| download | linux-de1fa15b6642f0b66f1844b9b464a8c28e84347c.tar.xz linux-de1fa15b6642f0b66f1844b9b464a8c28e84347c.zip | |
ipconfig: BOOTP: Request CONF_NAMESERVERS_MAX name servers
When ipconfig is autoconfigured via BOOTP, the request packet
initialised by ic_bootp_init_ext() always allocates 8 bytes for the name
server option, limiting the BOOTP server to responding with at most 2
name servers even though ipconfig in fact supports an arbitrary number
of name servers (as defined by CONF_NAMESERVERS_MAX, which is currently
3).
Only request name servers in the request packet if CONF_NAMESERVERS_MAX
is positive (to comply with [1, ยง3.8]), and allocate enough space in the
packet for CONF_NAMESERVERS_MAX name servers to indicate the maximum
number we can accept in response.
[1] RFC 2132, "DHCP Options and BOOTP Vendor Extensions":
https://tools.ietf.org/rfc/rfc2132.txt
Signed-off-by: Chris Novakovic <chris@chrisn.me.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'mm/page_io.c')
0 files changed, 0 insertions, 0 deletions