Displaying 14 results from an estimated 14 matches similar to: "Patch to improve malformed vorbiscomment handling"
2014 Sep 26
2
Patch to improve malformed vorbiscomment handling
Janne Hyv?rinen wrote:
> Patch v2, now handles more malformed cases. Original patch was for a
> file for which I had a sample from a user but this allows handling some
> manually broken test cases.
Err, I'm getting warning messages on that patch:
CC metadata_iterators.lo
metadata_iterators.c: In function ?read_metadata_block_data_vorbis_comment_cb_?:
2014 Sep 26
0
Patch to improve malformed vorbiscomment handling
Patch v2, now handles more malformed cases. Original patch was for a
file for which I had a sample from a user but this allows handling some
manually broken test cases.
On 25.9.2014 21:53, Janne Hyv?rinen wrote:
> Here's a patch to allow flac and metaflac handle files with malformed
> vorbiscomment metadata block.
>
>
> _______________________________________________
>
2014 Sep 26
0
Patch to improve malformed vorbiscomment handling
On 26.9.2014 15:21, Erik de Castro Lopo wrote:
> Janne Hyv?rinen wrote:
>
>> Patch v2, now handles more malformed cases. Original patch was for a
>> file for which I had a sample from a user but this allows handling some
>> manually broken test cases.
>
> Err, I'm getting warning messages on that patch:
>
> CC metadata_iterators.lo
>
2016 Mar 14
1
[PATCH] update obj->num_comments if short circuit in read_metadata_vorbiscomment_
In function read_metadata_vorbiscomment_ from stream_decoder.c, at
various locations where we short circuit the computation, we also set
`obj->num_comments` accordingly. For example:
https://git.xiph.org/?p=flac.git;a=blob;f=src/libFLAC/stream_decoder.c;h=e0f1b14d30dd548268a88e4341af3f38290816e3;hb=HEAD#l1736
2014 Sep 26
2
Patch to improve malformed vorbiscomment handling
Sorry for spamming but in the haste I forgot the stream_decoder part out.
On 26.9.2014 15:47, Janne Hyv?rinen wrote:
> On 26.9.2014 15:21, Erik de Castro Lopo wrote:
>> Janne Hyv?rinen wrote:
>>
>>> Patch v2, now handles more malformed cases. Original patch was for a
>>> file for which I had a sample from a user but this allows handling some
>>> manually
2007 Jul 14
2
PATCH : Fix missing protoypes
Hi all,
I added -Wmissing-prototypes -Wstrict-prototypes to the CFLAGS and
found that there were a number warnings generated.
The patch below fixes those warnings and adds the two -W flags to
configure.in.
Cheers,
Erik
----------------------8<----------------------8<----------------------
--- src/metaflac/operations_shorthand.h 1970-01-01 00:00:00 +0000
+++
2003 Oct 05
2
Possible security hole
Maybe security related mails should be sent elsewhere? I didn't notice
any so here it goes:
sender.c:receive_sums()
s->count = read_int(f);
..
s->sums = (struct sum_buf *)malloc(sizeof(s->sums[0])*s->count);
if (!s->sums) out_of_memory("receive_sums");
for (i=0; i < (int) s->count;i++) {
s->sums[i].sum1 = read_int(f);
2013 Sep 12
3
[PATCH 1/1 V3] x86/AMD-Vi: Add additional check for invalid special->handle
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
This patch handle additional cases for IVRS bugs where special->handle
is not correctly initialized for IOAPIC and HPETS due to firmware bugs.
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Provide logic in "is_ioapic_overidden()"
Signed-off-by: Jan Beulich <JBeulich@suse.com>
---
2003 Mar 30
1
[RFC][patch] dynamic rolling block and sum sizes II
Mark II of the patch set.
The first patch (dynsumlen2.patch) increments the protocol
version to support per-file dynamic block checksum sizes.
It is a prerequisite for varsumlen2.patch.
varsumlen2.patch implements per-file dynamic block and checksum
sizes.
The current block size calculation only applies to files
between 7MB and 160MB setting the block size to 1/10,0000 of
the file length for a
2012 Apr 05
2
[PATCH 2/2] V2: Use a single definition of MIN and MAX in sources
---
configure.ac | 7 +++++
src/libFLAC/bitreader.c | 12 ++-------
src/libFLAC/bitwriter.c | 8 ++----
src/libFLAC/fixed.c | 18 +++++--------
src/libFLAC/format.c | 8 ++----
src/libFLAC/include/private/macros.h | 29 ++++++++++++++++++++
src/libFLAC/metadata_iterators.c | 17 +++---------
2003 Mar 23
1
[RFC] dynamic checksum size
Currently rsync has a bit of a problem with very large
files. Dynamic block sizes were introduced to try handle that
automatically if the user didn't specify a block size.
Unfortunately that isn't enough and the block size would
need to grow faster than the file. Besides, overly large block
sizes mean large amounts of data need to be copied even for
small changes.
The maths indicate
2010 Dec 07
1
[ANNOUNCE] xorg-server 1.9.99.901
Ok, I think we've done enough damage for one release. Thanks everyone
for pulling a long weekend to get changes prepared and reviewed.
We're still missing the threaded input stuff, but that needs more review
and I think we wore Tiago out this time around. If someone wants to
propose merging it after the freeze, I think we should consider doing
it.
Note that this tarball depends on
2006 Aug 11
0
[PATCH] [4/5] SMBIOS -- generate SMBIOS tables
Add code to generate SMBIOS tables to hvmloader.
Signed-off-by: Andrew D. Ball <aball@us.ibm.com>
diff -r 1d817bfc5ed9 tools/firmware/hvmloader/Makefile
--- a/tools/firmware/hvmloader/Makefile Fri Aug 11 14:22:54 2006 +0100
+++ b/tools/firmware/hvmloader/Makefile Fri Aug 11 14:55:18 2006 -0400
@@ -31,7 +31,7 @@ DEFINES =-DDEBUG
DEFINES =-DDEBUG
XENINC =-I$(XEN_ROOT)/tools/libxc
2013 Jul 22
69
[xen-unstable] Commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, makes dom0 boot process stall several times.
Hi Jan,
After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times.
Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times.
(It also stalls on shutdown BTW)
I have