From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Stiffler Date: Thu, 1 Oct 2015 13:31:15 -0400 Subject: [U-Boot] [PATCH] net: Increase the size of the net_boot_file_name buffer In-Reply-To: <20151001142711.1CB7B3822C0@gemini.denx.de> References: <1443622325-30792-1-git-send-email-j-stiffler@ti.com> <20151001142711.1CB7B3822C0@gemini.denx.de> Message-ID: <560D6DE3.8070901@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 10/1/2015 10:27 AM, Wolfgang Denk wrote: > Dear Jacob, > > In message <1443622325-30792-1-git-send-email-j-stiffler@ti.com> you wrote: >> The net_boot_file_name buffer is used as storage for the bootfilename >> command line argument to network boot commands such as tftp and nfs. >> >> Increase the size of this buffer to 1024 bytes as the current size of >> 128 bytes is restrictive for arbitrary paths on the server. > According to RFC 2131, the boot file name has a fixed size of 128 > octets. Wolfgang, Yes. However, the global "net_boot_file_name" is not only used for BOOTP, but also for NFS and TFTP. "net_boot_file_name" appears to be temporary storage to supply the file path to arbitrary protocols from the command line arguments. The "file" field in the bootp message is fixed at 128 octets in the "bootp_hdr" structure. The contents of "net_boot_file_name" are read or written using the standard "strncopy()" or the similar "copy_filename()", so there should be any issue with respect to memory leaks. Thank you, Jacob Stiffler > Best regards, > > Wolfgang Denk >