From: Nikita Yushchenko <nyushchenko@dev.rtsoft.ru>
To: Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>,
Michael Thalmeier <michael.thalmeier@hale.at>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: arusalin <arusalin@dev.rtsoft.ru>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: pn533 driver crash
Date: Tue, 5 Jul 2016 16:56:44 +0300 [thread overview]
Message-ID: <577BBC9C.4030107@dev.rtsoft.ru> (raw)
Hi
We have ported pn533 driver from current upstream kernel to vendor
kernel that our target hardware runs, and are having crashes.
Analysis shows that same is possible in upstream kernel as well.
commit b31d5103c message states that pn533_recv_frame() can be entered
with dev->cmd not set. And in this case, change done by that commit
jumps directly to queue_work().
However, work routine pn533_wq_cmd_complete() unconditionally calls
pn533_send_async_complete(), and that unconditionally dereferences
dev->cmd. Thus crash.
Not yet sure how to fix that properly...
WBR,
Nikita Yushchenko
reply other threads:[~2016-07-05 14:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=577BBC9C.4030107@dev.rtsoft.ru \
--to=nyushchenko@dev.rtsoft.ru \
--cc=aloisio.almeida@openbossa.org \
--cc=arusalin@dev.rtsoft.ru \
--cc=lauro.venancio@openbossa.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thalmeier@hale.at \
--cc=sameo@linux.intel.com \
--cc=waldemar.rymarkiewicz@tieto.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox