[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250806162030.2deaa905530e182bbf939910@linux-foundation.org>
Date: Wed, 6 Aug 2025 16:20:30 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Jens Axboe <axboe@...nel.dk>, Minchan Kim <minchan@...nel.org>,
linux-kernel@...r.kernel.org, linux-block@...r.kernel.org, Seyediman
Seyedarab <imandevel@...il.com>
Subject: Re: [PATCH] zram: protect recomp_algorithm_show() with ->init_lock
On Wed, 6 Aug 2025 11:58:49 +0900 Sergey Senozhatsky <senozhatsky@...omium.org> wrote:
> > > Signed-off-by: Sergey Senozhatsky <senozhatsky@...omium.org>
> > > Reported-by: Seyediman Seyedarab <imandevel@...il.com>
> >
> > And including a Closes: for Seyediman's report (if it's publicly
> > linkable) would be great too, thanks.
> >
> > I'm guessing that a Fixes: isn't appropriate here because the
> > bug has been there since day 1.
>
> Yes, also there isn't really a public bug report there, I just noticed
> that while looking at some things that Seyediman was looking at. So I
> wanted to give Seyediman some credit. I suppose I probably should have
> added
> Suggested-by: Seyediman Seyedarab <imandevel@...il.com>
>
> instead.
Great, thanks.
> Should I send a v2?
Nope, I updated the changelog locally.
Powered by blists - more mailing lists