<feed xmlns='http://www.w3.org/2005/Atom'>
<title>jsnbd/web/js, branch master</title>
<subtitle>OpenBMC JavaScript NBD connector sources</subtitle>
<id>https://git.raptorcs.com/git/jsnbd/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/jsnbd/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/jsnbd/'/>
<updated>2019-03-27T00:54:38+00:00</updated>
<entry>
<title>js: Allow serving files &gt; 4GB in size</title>
<updated>2019-03-27T00:54:38+00:00</updated>
<author>
<name>Jeremy Kerr</name>
<email>jk@ozlabs.org</email>
</author>
<published>2019-03-25T08:30:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/jsnbd/commit/?id=bcc6cc5bcadb20005ae03c8c4a4eb87006f0d222'/>
<id>urn:sha1:bcc6cc5bcadb20005ae03c8c4a4eb87006f0d222</id>
<content type='text'>
Currently, the javascript NBD server only handles files of sizes that
are representable in 32 bits.

Although we can't do full 64-bit offsets with Javascript's number
representation, we should be able to handle up to
Number.MAX_SAFE_INTEGER. This change adds support for using the top-32
bit field in file sizes and read request offsets.

Reported-by: Lei YU &lt;mine260309@gmail.com&gt;
Signed-off-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;
Change-Id: I41dee58c3913cba49c5cd73ebdd5d6fb56786d25
</content>
</entry>
<entry>
<title>Initial js/nbd commit</title>
<updated>2018-07-26T04:14:56+00:00</updated>
<author>
<name>Jeremy Kerr</name>
<email>jk@ozlabs.org</email>
</author>
<published>2018-07-26T04:14:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/jsnbd/commit/?id=f403c420060f7735ba7c4cdc8eef49ff336a5c70'/>
<id>urn:sha1:f403c420060f7735ba7c4cdc8eef49ff336a5c70</id>
<content type='text'>
Signed-off-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;
</content>
</entry>
</feed>
