<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/streaming.c, branch v2.10.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.10.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.10.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2016-09-26T17:48:03Z</updated>
<entry>
<title>streaming: make sure to notice corrupt object</title>
<updated>2016-09-26T17:48:03Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-09-26T16:23:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=97026fe9a6f70b6c0a9e09408a504287c13dea43'/>
<id>urn:sha1:97026fe9a6f70b6c0a9e09408a504287c13dea43</id>
<content type='text'>
The streaming read interface from a loose object called
parse_sha1_header() but discarded its return value, without noticing
a potential error.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'sb/plug-streaming-leak'</title>
<updated>2015-04-14T18:49:09Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-04-14T18:49:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d2ae751b1cae0674e0a1f7fe4da0a341365cefbb'/>
<id>urn:sha1:d2ae751b1cae0674e0a1f7fe4da0a341365cefbb</id>
<content type='text'>
* sb/plug-streaming-leak:
  streaming.c: fix a memleak
</content>
</entry>
<entry>
<title>streaming.c: fix a memleak</title>
<updated>2015-03-31T19:14:42Z</updated>
<author>
<name>John Keeping</name>
<email>john@keeping.me.uk</email>
</author>
<published>2015-03-31T01:22:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9ce4ad3e0eac33b4cae38ebd76c26ddba2468631'/>
<id>urn:sha1:9ce4ad3e0eac33b4cae38ebd76c26ddba2468631</id>
<content type='text'>
When stream_blob_to_fd() opens an input stream with a filter, the
filter gets discarded upon calling close_istream() before the
function returns in the normal case.  However, when we fail to open
the stream, we failed to discard the filter.

By discarding the filter in the failure case, give a consistent
life-time rule of the filter to the callers; otherwise the callers
need to conditionally discard the filter themselves, and this
function does not give enough hint for the caller to do so
correctly.

Signed-off-by: John Keeping &lt;john@keeping.me.uk&gt;
Signed-off-by: Stefan Beller &lt;sbeller@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>open_istream(): do not dereference NULL in the error case</title>
<updated>2014-02-19T00:00:53Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-02-19T00:00:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=78368f2c1ad342719ccf1e719bd5126ca6c7b68b'/>
<id>urn:sha1:78368f2c1ad342719ccf1e719bd5126ca6c7b68b</id>
<content type='text'>
When stream-filter cannot be attached, it is expected to return NULL,
and we should close the stream we opened and signal an error by
returning NULL ourselves from this function.

However, we attempted to dereference that NULL pointer between the
point we detected the error and returned from the function.

Brought-to-attention-by: John Keeping &lt;john@keeping.me.uk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ef/mingw-write'</title>
<updated>2014-01-27T18:44:59Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-01-27T18:44:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7b4e2b7e6aba677fcefffde79d0d3a53ae623b4f'/>
<id>urn:sha1:7b4e2b7e6aba677fcefffde79d0d3a53ae623b4f</id>
<content type='text'>
* ef/mingw-write:
  mingw: remove mingw_write
  prefer xwrite instead of write
</content>
</entry>
<entry>
<title>prefer xwrite instead of write</title>
<updated>2014-01-17T20:09:26Z</updated>
<author>
<name>Erik Faye-Lund</name>
<email>kusmabite@gmail.com</email>
</author>
<published>2014-01-17T14:17:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7edc02f4deedb3a11abeb328dc2596b2886c2f47'/>
<id>urn:sha1:7edc02f4deedb3a11abeb328dc2596b2886c2f47</id>
<content type='text'>
Our xwrite wrapper already deals with a few potential hazards, and
are as such more robust. Prefer it instead of write to get the
robustness benefits everywhere.

Signed-off-by: Erik Faye-Lund &lt;kusmabite@gmail.com&gt;
Reviewed-and-improved-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>sha1_object_info_extended(): add an "unsigned flags" parameter</title>
<updated>2013-12-12T19:53:48Z</updated>
<author>
<name>Christian Couder</name>
<email>chriscool@tuxfamily.org</email>
</author>
<published>2013-12-11T07:46:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=de7b5d6218e4b928c5a395e34e5e1de40fae2a0d'/>
<id>urn:sha1:de7b5d6218e4b928c5a395e34e5e1de40fae2a0d</id>
<content type='text'>
This parameter is not used yet, but it will be used to tell
sha1_object_info_extended() if it should perform object
replacement or not.

Signed-off-by: Christian Couder &lt;chriscool@tuxfamily.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jk/cat-file-batch-optim'</title>
<updated>2013-07-25T02:21:21Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2013-07-25T02:21:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=356df9bd8df58eb759fedaee8a8d1a7dc0872f8f'/>
<id>urn:sha1:356df9bd8df58eb759fedaee8a8d1a7dc0872f8f</id>
<content type='text'>
If somebody wants to only know on-disk footprint of an object
without having to know its type or payload size, we can bypass a
lot of code to cheaply learn it.

* jk/cat-file-batch-optim:
  Fix some sparse warnings
  sha1_object_info_extended: pass object_info to helpers
  sha1_object_info_extended: make type calculation optional
  packed_object_info: make type lookup optional
  packed_object_info: hoist delta type resolution to helper
  sha1_loose_object_info: make type lookup optional
  sha1_object_info_extended: rename "status" to "type"
  cat-file: disable object/refname ambiguity check for batch mode
</content>
</entry>
<entry>
<title>open_istream: remove unneeded check for null pointer</title>
<updated>2013-07-23T18:35:18Z</updated>
<author>
<name>Stefan Beller</name>
<email>stefanbeller@googlemail.com</email>
</author>
<published>2013-07-23T13:16:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6a907786af835ac15962be53f1492f23e044f479'/>
<id>urn:sha1:6a907786af835ac15962be53f1492f23e044f479</id>
<content type='text'>
'st' is allocated via xmalloc a few lines before and passed to
the stream opening functions.
The xmalloc function is written in a way that either 'st' is allocated
valid memory or xmalloc already dies.
The function calls to open_istream_* do not change 'st', as the pointer is
passed by reference and not a pointer of a pointer.

Hence 'st' cannot be null at that part of the code.

Signed-off-by: Stefan Beller &lt;stefanbeller@googlemail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Fix some sparse warnings</title>
<updated>2013-07-18T23:43:47Z</updated>
<author>
<name>Ramsay Jones</name>
<email>ramsay@ramsay1.demon.co.uk</email>
</author>
<published>2013-07-18T20:25:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d099b7173dabdeeb1f339151ac2169b3a91bf631'/>
<id>urn:sha1:d099b7173dabdeeb1f339151ac2169b3a91bf631</id>
<content type='text'>
Sparse issues some "Using plain integer as NULL pointer" warnings.
Each warning relates to the use of an '{0}' initialiser expression
in the declaration of an 'struct object_info'. The first field of
this structure has pointer type. Thus, in order to suppress these
warnings, we replace the initialiser expression with '{NULL}'.

Signed-off-by: Ramsay Jones &lt;ramsay@ramsay1.demon.co.uk&gt;
Acked-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
