From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Reinhard Speyerer <rspmn@arcor.de>
Cc: Gregor Jasny <gjasny@googlemail.com>,
Clemens Ladisch <clemens@ladisch.de>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] libdvbv5: T2 delivery descriptor: fix wrong size of bandwidth field
Date: Sun, 7 May 2017 08:43:33 -0300 [thread overview]
Message-ID: <20170507084233.037ec0c3@vento.lan> (raw)
In-Reply-To: <20170504231429.GA1997@arcor.de>
Em Fri, 5 May 2017 01:14:29 +0200
Reinhard Speyerer <rspmn@arcor.de> escreveu:
> Hi Gregor and Mauro,
>
> For some reason several/most(?) programs from freenet.TV (connect) which
> are distributed via the Internet instead of DVB-T2 have duplicate entries.
Found the issue. There's a logic inside the scan algorithm that groups
multi-section tables. There was a mistake there with was causing it to
read twice the first section. As, on most cases, the SDT table has just
one section, nobody noticed it so far. Just added a patch, on both master
and stable fixing this issue, as enclosed.
Thanks for reporting it!
Regards,
Mauro
-
[PATCH] dvb-scan: fix the logic for multi-section handling
The logic that parses multisection handling is broken.
Right now, it parses twice the initial section, causing
duplicated entries at the tables.
The net result is that, on tables like SDT, channels
appear duplicated. Before this patch, what was happening
was:
dvb_read_sections: waiting for table ID 0x42, program ID 0x11
dvb_parse_section: received table 0x42, extension ID 0x4072, section 0/1
dvb_parse_section: received table 0x42, extension ID 0x4072, section 1/1
dvb_parse_section: received table 0x42, extension ID 0x4072, section 0/1
dvb_parse_section: table 0x42, extension ID 0x4072: done
So, section 0/1 were parsed twice. After that, it now properly
detects that section 0/1 was already parsed:
dvb_read_sections: waiting for table ID 0x42, program ID 0x11
dvb_parse_section: received table 0x42, extension ID 0x4072, section 0/1
dvb_parse_section: received table 0x42, extension ID 0x4072, section 1/1
dvb_parse_section: table 0x42, extension ID 0x4072: done
Reported-by: Reinhard Speyerer <rspmn@arcor.de>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
diff --git a/lib/libdvbv5/dvb-scan.c b/lib/libdvbv5/dvb-scan.c
index 07fe13e808a8..7ff8ba4f0446 100644
--- a/lib/libdvbv5/dvb-scan.c
+++ b/lib/libdvbv5/dvb-scan.c
@@ -239,12 +239,6 @@ static int dvb_parse_section(struct dvb_v5_fe_parms_priv *parms,
return -1;
}
ext += i;
-
- memset(ext, 0, sizeof(*ext));
- ext->ext_id = h.id;
- ext->first_section = h.section_id;
- ext->last_section = h.last_section;
- new = 1;
}
}
prev parent reply other threads:[~2017-05-07 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 15:50 [PATCH] libdvbv5: T2 delivery descriptor: fix wrong size of bandwidth field Clemens Ladisch
2017-05-02 20:30 ` Gregor Jasny
2017-05-02 20:49 ` Mauro Carvalho Chehab
2017-05-03 12:53 ` Mauro Carvalho Chehab
2017-05-03 22:33 ` Mauro Carvalho Chehab
2017-05-04 7:55 ` Gregor Jasny
2017-05-04 12:11 ` Mauro Carvalho Chehab
2017-05-04 23:14 ` Reinhard Speyerer
2017-05-05 0:37 ` Mauro Carvalho Chehab
2017-05-07 11:43 ` Mauro Carvalho Chehab [this message]
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=20170507084233.037ec0c3@vento.lan \
--to=mchehab@s-opensource.com \
--cc=clemens@ladisch.de \
--cc=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=rspmn@arcor.de \
/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).