summaryrefslogtreecommitdiffstats
path: root/drivers/nfc/s3fwrn5
diff options
context:
space:
mode:
authorJohan Hovold <johan@kernel.org>2017-03-30 12:15:37 +0200
committerSamuel Ortiz <sameo@linux.intel.com>2017-06-18 23:57:59 +0200
commit0cbe40112f42cf5e008f9127f6cd5952ba3946c7 (patch)
treee66412b03cf38900db3ba3bede52fe9a3a45de30 /drivers/nfc/s3fwrn5
parentNFC: nfcmrvl_uart: add missing tty-device sanity check (diff)
downloadlinux-0cbe40112f42cf5e008f9127f6cd5952ba3946c7.tar.xz
linux-0cbe40112f42cf5e008f9127f6cd5952ba3946c7.zip
NFC: nfcmrvl: do not use device-managed resources
This specifically fixes resource leaks in the registration error paths. Device-managed resources is a bad fit for this driver as devices can be registered from the n_nci line discipline. Firstly, a tty may not even have a corresponding device (should it be part of a Unix98 pty) something which would lead to a NULL-pointer dereference when registering resources. Secondly, if the tty has a class device, its lifetime exceeds that of the line discipline, which means that resources would leak every time the line discipline is closed (or if registration fails). Currently, the devres interface was only being used to request a reset gpio despite the fact that it was already explicitly freed in nfcmrvl_nci_unregister_dev() (along with the private data), something which also prevented the resource leak at close. Note that the driver treats gpio number 0 as invalid despite it being perfectly valid. This will be addressed in a follow-up patch. Fixes: b2fe288eac72 ("NFC: nfcmrvl: free reset gpio") Fixes: 4a2b947f56b3 ("NFC: nfcmrvl: add chip reset management") Cc: stable <stable@vger.kernel.org> # 4.2: b2fe288eac72 Cc: Vincent Cuissard <cuissard@marvell.com> Signed-off-by: Johan Hovold <johan@kernel.org> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'drivers/nfc/s3fwrn5')
0 files changed, 0 insertions, 0 deletions