From: Ang Way Chuang <wcang79@gmail.com>
To: linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Hilmar Linder <hlinder@cosy.sbg.ac.at>,
Wolfram Stering <wstering@cosy.sbg.ac.at>
Subject: [PATCH] dvb-core: Fix ULE decapsulation bug when less than 4 bytes of ULE SNDU is packed into the remaining bytes of a MPEG2-TS frame
Date: Tue, 17 Nov 2009 17:56:33 +0800 [thread overview]
Message-ID: <51d384e10911170156x1e8f18afh48369a4cd664b45f@mail.gmail.com> (raw)
ULE (Unidirectional Lightweight Encapsulation RFC 4326) decapsulation
code has a bug that incorrectly treats ULE SNDU packed into the remaining
2 or 3 bytes of a MPEG2-TS frame as having invalid pointer field on the
subsequent MPEG2-TS frame.
This patch was generated against v2.6.32-rc7, however it wasn't tested
using that kernel. Similar patch was applied and tested using 2.6.27 which
is similar to the latest dvb_net.c, except for network device statistical data
structure. I suspect that this bug was introduced in kernel version 2.6.15,
but had not verified it.
Care has been taken not to introduce more bug by fixing this bug, but
please scrutinize the code for I always produces buggy code.
Signed-off-by: Ang Way Chuang <wcang@nav6.org>
next reply other threads:[~2009-11-17 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:56 Ang Way Chuang [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-17 10:00 [PATCH] dvb-core: Fix ULE decapsulation bug when less than 4 bytes of ULE SNDU is packed into the remaining bytes of a MPEG2-TS frame Ang Way Chuang
2009-11-23 9:37 Ang Way Chuang
2009-11-24 1:34 ` Ang Way Chuang
2009-11-24 8:00 ` Dan Carpenter
2009-11-24 8:04 ` Ang Way Chuang
2009-11-24 8:07 ` Ang Way Chuang
2010-05-06 14:52 Ang Way Chuang
2010-05-27 5:02 Ang Way Chuang
2010-05-27 12:30 ` Jarod Wilson
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=51d384e10911170156x1e8f18afh48369a4cd664b45f@mail.gmail.com \
--to=wcang79@gmail.com \
--cc=hlinder@cosy.sbg.ac.at \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=wstering@cosy.sbg.ac.at \
/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).