lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 15 Feb 2014 12:38:11 -0800 From: Greg KH <gregkh@...uxfoundation.org> To: Larry Finger <Larry.Finger@...inger.net> Cc: devel@...verdev.osuosl.org, netdev@...r.kernel.org Subject: Re: [PATCH 10/13] staging: r8188eu: Remove wrapper _enter_critical_mutex() On Fri, Feb 14, 2014 at 04:54:14PM -0600, Larry Finger wrote: > This wrapper returned the result of mutex_lock_interruptible(); however, > none of the callers checked the returned value. Then why is the code logic changing? > > As a result of a gcc upgrade to version 4.8.1, two false unitialized variable > warnings appeared. To silence the warnings, they are initialized to 0. > > Signed-off-by: Larry Finger <Larry.Finger@...inger.net> > --- > drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 3 ++- > drivers/staging/rtl8188eu/hal/usb_ops_linux.c | 8 +++++--- > drivers/staging/rtl8188eu/include/osdep_service.h | 9 --------- > drivers/staging/rtl8188eu/os_dep/os_intfs.c | 3 ++- > 4 files changed, 9 insertions(+), 14 deletions(-) > > diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c > index c197b22..e95a1ba 100644 > --- a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c > +++ b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c > @@ -4429,7 +4429,8 @@ s32 dump_mgntframe_and_wait_ack(struct adapter *padapter, struct xmit_frame *pmg > if (padapter->bSurpriseRemoved || padapter->bDriverStopped) > return -1; > > - _enter_critical_mutex(&pxmitpriv->ack_tx_mutex, NULL); > + if (mutex_lock_interruptible(&pxmitpriv->ack_tx_mutex)) > + return -1; That's not what the original code did, so this change could cause problems, right? > -static inline int _enter_critical_mutex(struct mutex *pmutex, > - unsigned long *pirqL) > -{ > - int ret; > - > - ret = mutex_lock_interruptible(pmutex); > - return ret; > -} This didn't affect the caller function's code path... I've applied this series up to here. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists