From: Romain Baeriswyl <Romain.Baeriswyl@abilis.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Christian Ruppert <chrisr@abilis.com>,
Ole Ernst <olebowle@gmx.com>,
linux-media@vger.kernel.org
Subject: Linux DVB frontend issue
Date: Mon, 26 May 2014 16:17:48 +0200 (CEST) [thread overview]
Message-ID: <1586019348.6279.1401113868322.JavaMail.root@abilis.com> (raw)
In-Reply-To: <832879218.6141.1401112530064.JavaMail.root@abilis.com>
Dear Mauro,
We are using the Linux DVB frontend module on our platform and
we are facing an issue when having concurrent calls with FE_SET_FRONTEND
and FE_GET_FRONTEND ioctl.
Issue is that both ioctls are using the same dtv_property_cache buffer.
If a FE_SET_FRONTEND ioctl is interrupted by a FE_GET_FRONTEND then the
dtv_property_cache is overwritten with the result of the FE_GET_FRONTEND.
When the FE_SET_FRONTEND operation resumes, the dtv_property_cache may
not be accurate anymore.
Did you already face this issue?
Up to now I tried, without success, to think on a fix that does not impact
too much the existing code.
One solution could be to have one cache for reading properties and one other
cache for writing properties, but this will impact all the drivers below
the DVB frontend.
Do you see another less impacting solution?
Best regards,
Romain Baeriswyl
Abilis Systems
3, chemin Pré Fleuri
CH-1228 Plan-Les-Ouates
Geneva
next parent reply other threads:[~2014-05-26 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <832879218.6141.1401112530064.JavaMail.root@abilis.com>
2014-05-26 14:17 ` Romain Baeriswyl [this message]
2014-05-26 16:03 ` Linux DVB frontend issue Mauro Carvalho Chehab
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=1586019348.6279.1401113868322.JavaMail.root@abilis.com \
--to=romain.baeriswyl@abilis.com \
--cc=chrisr@abilis.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=olebowle@gmx.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.