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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 8 Aug 2018 22:34:20 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Frank Werner-Krippendorf <mail@...pp.ch>,
        devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
        Larry.Finger@...inger.net
Subject: Re: [PATCH] Staging:rtl8712: Style - Removed inline block comment to
 fix "Statements should start on a tapstop"

On Wed, Aug 08, 2018 at 11:22:57AM +0200, Greg KH wrote:
> On Sun, Aug 05, 2018 at 09:41:06PM +0200, Frank Werner-Krippendorf wrote:
> > Removed 5 inline comments "/*volatile*/" rtl87x_event.h, to fix
> > a coding style issue "Statements should start on a tabstop"
> > detected by checkpatch.pl script.
> > 
> > Signed-off-by: Frank Werner-Krippendorf <mail@...pp.ch>
> > ---
> >  drivers/staging/rtl8712/rtl871x_event.h | 10 +++++-----
> >  1 file changed, 5 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/staging/rtl8712/rtl871x_event.h b/drivers/staging/rtl8712/rtl871x_event.h
> > index 5171379..2e59e8e 100644
> > --- a/drivers/staging/rtl8712/rtl871x_event.h
> > +++ b/drivers/staging/rtl8712/rtl871x_event.h
> > @@ -90,13 +90,13 @@ struct event_node {
> >  	unsigned char *node;
> >  	unsigned char evt_code;
> >  	unsigned short evt_sz;
> > -	/*volatile*/ int *caller_ff_tail;
> > +	int *caller_ff_tail;
> >  	int	caller_ff_sz;
> >  };
> >  
> >  struct c2hevent_queue {
> > -	/*volatile*/ int	head;
> > -	/*volatile*/ int	tail;
> 
> Those "volatile" seem to imply that something is needed for these
> variables.  Please check to ensure that these are ok to remove in that
> there is the proper locking for these types of things.
> 

Good news, people!  I have done the audit and there is no locking bug.
These structs can be deleted because they aren't ever used.

Frank, please can you resend?  There may be more unused stuff in here
which I didn't see.

regards,
dan carpenter

Powered by blists - more mailing lists