On 2020-08-11 14:34, Shawn Webb wrote:
If you use git, you can easily cherry-pick the fix from HardenedBSD:
Hi,
There is atomic_clear_rel_long() which does the release in addition to
clearing. See:
https://svnweb.freebsd.org/changeset/base/364110
I used a macro, in case it is not
If you use git, you can easily cherry-pick the fix from HardenedBSD:
https://github.com/HardenedBSD/hardenedBSD/commit/e7ee74598b987fdc702614668b7ea85884289cf1
On Tue, Aug 11, 2020 at 02:31:26PM +0200, Mateusz Guzik wrote:
> Hi. This remains unfixed.
>
> On 8/4/20, Emmanuel Vadot wrote:
> > On
Hi. This remains unfixed.
On 8/4/20, Emmanuel Vadot wrote:
> On Tue, 4 Aug 2020 13:11:02 -0500
> Alan Cox wrote:
>
>>
>> On 8/4/20 10:25 AM, Emmanuel Vadot wrote:
>> > Author: manu
>> > Date: Tue Aug 4 15:25:22 2020
>> > New Revision: 363842
>> > URL:
On Tue, 4 Aug 2020 13:11:02 -0500
Alan Cox wrote:
>
> On 8/4/20 10:25 AM, Emmanuel Vadot wrote:
> > Author: manu
> > Date: Tue Aug 4 15:25:22 2020
> > New Revision: 363842
> > URL: https://svnweb.freebsd.org/changeset/base/363842
> >
> > Log:
> >linuxkpi: Add clear_bit_unlock
> >
> >
On 8/4/20 10:25 AM, Emmanuel Vadot wrote:
Author: manu
Date: Tue Aug 4 15:25:22 2020
New Revision: 363842
URL: https://svnweb.freebsd.org/changeset/base/363842
Log:
linuxkpi: Add clear_bit_unlock
This calls clear_bit and adds a memory barrier.
Sponsored by: The FreeBSD
Author: manu
Date: Tue Aug 4 15:25:22 2020
New Revision: 363842
URL: https://svnweb.freebsd.org/changeset/base/363842
Log:
linuxkpi: Add clear_bit_unlock
This calls clear_bit and adds a memory barrier.
Sponsored by: The FreeBSD Foundation
Reviewed by: hselasky
MFC after:1
