Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #63361 > unrolled thread

Bug#886049: Further splice() tests with and without libglib2.0-0

Started byChristoph Biedl <debian.axhn@manchmal.in-ulm.de>
First post2019-02-13 18:40 +0100
Last post2019-02-13 18:40 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#886049: Further splice() tests with and without libglib2.0-0 Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2019-02-13 18:40 +0100

#63361 — Bug#886049: Further splice() tests with and without libglib2.0-0

FromChristoph Biedl <debian.axhn@manchmal.in-ulm.de>
Date2019-02-13 18:40 +0100
SubjectBug#886049: Further splice() tests with and without libglib2.0-0
Message-ID<xr6FQ-3X3-9@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Reiny wrote...

> About the above mentioned bug I did some more tests: I built a debug version
> of the libglib2.0-0 to see what is happening inside where the splice
> function is called. In case of a small file with 112 bytes the splice() is
> called inside the function do_splice() in gfile.c for three times:
(...)

At first, thanks a lot for your analysis.

Now my question, does this still happen in buster or sid? Since I could not
reproduce the problem in buster, but very well in Ubuntu Bionic, I assume
it has been healed the the past weeks, possibly by the latest glib2 upstream
release - although I didn't find anything obvious in the sources.

    Christoph

[toc] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web