From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4842] Clarified filename handling, by Johannes Schindelin.
Date: Thu, 03 Jul 2008 19:54:21 +0000 [thread overview]
Message-ID: <E1KEUsn-00085O-4b@cvs.savannah.gnu.org> (raw)
Revision: 4842
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4842
Author: ths
Date: 2008-07-03 19:54:19 +0000 (Thu, 03 Jul 2008)
Log Message:
-----------
Clarified filename handling, by Johannes Schindelin.
Modified Paths:
--------------
trunk/block-vvfat.c
Modified: trunk/block-vvfat.c
===================================================================
--- trunk/block-vvfat.c 2008-07-03 18:51:23 UTC (rev 4841)
+++ trunk/block-vvfat.c 2008-07-03 19:54:19 UTC (rev 4842)
@@ -1410,7 +1410,12 @@
}
typedef struct {
- unsigned char name[1024];
+ /*
+ * Since the sequence number is at most 0x3f, and the filename
+ * length is at most 13 times the sequence number, the maximal
+ * filename length is 0x3f * 13 bytes.
+ */
+ unsigned char name[0x3f * 13 + 1];
int checksum, len;
int sequence_number;
} long_file_name;
reply other threads:[~2008-07-03 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1KEUsn-00085O-4b@cvs.savannah.gnu.org \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.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).