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] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230225205749.2effb5f902dee8919704f3cd@linux-foundation.org>
Date:   Sat, 25 Feb 2023 20:57:49 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Geert Uytterhoeven <geert+renesas@...der.be>,
        Minchan Kim <minchan@...nel.org>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] zram: Use atomic_long_read() to read atomic_long_t

On Sat, 25 Feb 2023 20:30:52 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:

> > Fix this by using atomic_long_read() instead.
> > 
> > Reported-by; noreply@...erman.id.au
> 
> That's an interesting one.  Was this mpe@?
> 
> I like it when a Reported-by: is followed by a Link: to the report, so
> I can go hunt down such things.

I found this, and added it to the changelog:

Reported-by: kernel test robot <lkp@...el.com>
  Link: https://lore.kernel.org/oe-kbuild-all/202302241840.nwdXqE5r-lkp@intel.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ