projects / GitHub / moto-9609 / android_kernel_motorola_exynos9610.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d1f0f31) | patch
staging: rtl8192e: don't just print an error and continue
authorDan Carpenter <dan.carpenter@oracle.com>
Tue, 28 Jul 2015 15:49:25 +0000 (18:49 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 31 Jul 2015 23:18:43 +0000 (16:18 -0700)
commita9cf7250ba85427a372225067d57cf3ff4471047
treee0d42f3171b7d61a3c2aa8ea4a45f9afc859cf9btree | snapshot (tar.gz zip)
parentd1f0f3118e55ad80136d19dd4afdb32ccba26a42commit | diff
staging: rtl8192e: don't just print an error and continue

I was looking at how TOTAL_CAM_ENTRY is used and I saw this code.  We
print an error but continue writing "EntryNo" to a register as if it
were valid.  "EntryNo" is controlled by the user in rtl8192_ioctl() so
it definitely can be invalid.  I'm not positive what happens with the
invalid data but it can't be good.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/rtl8192e/rtl8192e/rtl_cam.c diff | blob | blame | history