linux-kernel - Re: [PATCH 2/2] zram: fixup read_block

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 for Android: free password hash cracker in your pocket

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

Message-ID: <wstf2ujpdkz5evedgqr2awze7wdwcmcluxntkqk2eifp5axjpu@lawhwffyeg72>
Date: Fri, 16 Jan 2026 07:54:25 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, Chris Mason <clm@...a.com>
Subject: Re: [PATCH 2/2] zram: fixup read_block_state()

On (26/01/15 14:07), Andrew Morton wrote:
> On Thu, 15 Jan 2026 12:30:06 +0900 Sergey Senozhatsky <senozhatsky@...omium.org> wrote:
> 
> > ac_time is now in seconds, do not use ktime_to_timespec64()
> 
> Please help me out here - which patch introduced the issue which Chris
> found?

This one:
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/zram-use-u32-for-entry-ac_time-tracking.patch

> > Reported-by: Chris Mason <clm@...a.com>
> 
> The Closes: link would be helpful.

I thought that for fixup patches that are still in your tree we
don't need Closes: tags.  If you prefer to have them, it should
be this email:
http://lore.kernel.org/linux-kernel/20260114124522.1326519-1-clm@meta.com

[..]
> > -		ts = ktime_to_timespec64(zram->table[index].attr.ac_time);
> >  		copied = snprintf(kbuf + written, count,
> > -			"%12zd %12lld.%06lu %c%c%c%c%c%c\n",
> > -			index, (s64)ts.tv_sec,
> > -			ts.tv_nsec / NSEC_PER_USEC,
> > +			"%12zd %12u.%06lu %c%c%c%c%c%c\n",
> > +			index, zram->table[index].attr.ac_time, 0,
> 
> local `ts' is now unused?

Oh, yes.  Somehow my compiler didn't notice that.