linux-kernel - Re: [PATCH] staging: vc04_services: replace g_free_fragments

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 28 Oct 2019 16:37:04 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Davidlohr Bueso <dave@...olabs.net>
Cc:     Stefan Wahren <wahrenst@....net>, eric@...olt.net,
        linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org
Subject: Re: [PATCH] staging: vc04_services: replace g_free_fragments_mutex
 with spinlock

On Mon, Oct 28, 2019 at 08:21:08AM -0700, Davidlohr Bueso wrote:
> On Mon, 28 Oct 2019, Stefan Wahren wrote:
> 
> > Hi Davidlohr,
> > 
> > Am 27.10.19 um 23:15 schrieb Davidlohr Bueso:
> > > There seems no need to be using a semaphore, or a sleeping lock
> > > in the first place: critical region is extremely short, does not
> > > call into any blocking calls and furthermore lock and unlocking
> > > operations occur in the same context.
> > > 
> > > Get rid of another semaphore user by replacing it with a spinlock.
> > > 
> > > Signed-off-by: Davidlohr Bueso <dave@...olabs.net>
> > > ---
> > > This is in an effort to further reduce semaphore users in the kernel.
> > > 
> > thanks for this. Could please also send this to devel@...verdev.osuosl.org?
> 
> Ccing.

I don't see a patch here :(