From: Stephan Trebels <stephan@trebels.com>
To: linux-media@vger.kernel.org
Cc: stephan@trebels.com
Subject: [libdvben50221] stack leaks resources on non-MMI session reconnect
Date: Thu, 15 Jul 2010 15:20:14 +0200 [thread overview]
Message-ID: <1279200014.14890.33.camel@stephan-laptop> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 868 bytes --]
The issue was, that LIBDVBEN50221 did not allow a CAM to re-establish
the session holding non-MMI resources if using the lowlevel interface.
The session_number was recorded on open, but not freed on close (which
IMO is an bug in the code, I attach the scaled down hg changeset). With
this change, the SMIT CAM with a showtime card works fine according to
tests so far.
The effect was, that the CAM tried to constantly close and re-open the
session and the LIBDVBEN50221 kept telling it, that the resource is
already allocated to a different session. Additionally this caused the
library to use the _old_ session number in communications with the CAM,
which did not even exist anymore, so caused all writes of CA PMTs to
fail with EINTR.
Stephan
P.S. If there is a better place to report user-space library bugs for
linuxtv, please let me know.
[-- Attachment #1.2: dvb-apps-ca-session-leak.changeset --]
[-- Type: text/plain, Size: 1450 bytes --]
# HG changeset patch
# User Stephan Trebels <stephan@trebels.com>
# Date 1279192697 -3600
# Node ID 12928658e57ea046b35dfab485f23559b3036d42
# Parent 4ba933ff13fbd619be9bdbbf097b8dbfe0fbf679
Correctly free resources when a session is closed. This allows a CAM module to re-open a session.
diff -r 4ba933ff13fb -r 12928658e57e lib/libdvben50221/en50221_stdcam_llci.c
--- a/lib/libdvben50221/en50221_stdcam_llci.c Sat Jul 03 15:25:16 2010 +0200
+++ b/lib/libdvben50221/en50221_stdcam_llci.c Thu Jul 15 12:18:17 2010 +0100
@@ -374,14 +374,21 @@
} else if (resource_id == EN50221_APP_MMI_RESOURCEID) {
llci->stdcam.mmi_session_number = session_number;
}
+ break;
+ case S_SCALLBACK_REASON_CLOSE:
+ if (resource_id == EN50221_APP_MMI_RESOURCEID) {
+ llci->stdcam.mmi_session_number = -1;
+ } else if (resource_id == EN50221_APP_DATETIME_RESOURCEID) {
+ llci->datetime_session_number = -1;
+ } else if (resource_id == EN50221_APP_AI_RESOURCEID) {
+ llci->stdcam.ai_session_number = -1;
+ } else if (resource_id == EN50221_APP_CA_RESOURCEID) {
+ llci->stdcam.ca_session_number = -1;
+ } else if (resource_id == EN50221_APP_MMI_RESOURCEID) {
+ llci->stdcam.mmi_session_number = -1;
+ }
break;
- case S_SCALLBACK_REASON_CLOSE:
- if (resource_id == EN50221_APP_MMI_RESOURCEID) {
- llci->stdcam.mmi_session_number = -1;
- }
-
- break;
}
return 0;
}
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-07-15 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 13:20 Stephan Trebels [this message]
2010-08-08 21:53 ` [libdvben50221] stack leaks resources on non-MMI session reconnect DUBOST Brice
2010-11-02 10:15 ` DUBOST Brice
2010-11-02 10:38 ` Stephan Trebels
2010-11-02 16:18 ` pierre.gronlier
-- strict thread matches above, loose matches on Subject: below --
2010-11-07 20:41 Ludovic BOUE
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=1279200014.14890.33.camel@stephan-laptop \
--to=stephan@trebels.com \
--cc=linux-media@vger.kernel.org \
/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).