linux-ext4 - Re: [PATCH] ext4: change variable "count" to signed integer

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 PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

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

Date:   Mon, 20 Jun 2022 08:45:14 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     Theodore Ts'o <tytso@....edu>
Cc:     adilger.kernel@...ger.ca,
        Ding Xiang <dingxiang@...s.chinamobile.com>,
        linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
        Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Subject: Re: [PATCH] ext4: change variable "count" to signed integer

On Sat, Jun 18, 2022 at 06:22:00PM -0400, Theodore Ts'o wrote:
> On Sat, Jun 18, 2022 at 12:33:01PM +0300, Dan Carpenter wrote:
> > On Fri, Jun 17, 2022 at 10:59:01PM -0400, Theodore Ts'o wrote:
> > > On Mon, 30 May 2022 18:00:47 +0800, Ding Xiang wrote:
> > > > Since dx_make_map() may return -EFSCORRUPTED now,
> > > > so change "count" to signed integer.
> > > > 
> > > > 
> > > 
> > > Applied, thanks!
> > > 
> > > [1/1] ext4: change variable "count" to signed integer
> > >       commit: fefb759df063599ad483422eb07ef8e14c612cc2
> > > 
> > 
> > There was some kind of process error here...
> > 
> > 1) That commit somehow never made it to linux-next.
> 
> That's I only pushed it out Friday night (US/Eastern), and Stephen
> Rothwell creates new linux-next release based on snapshots taken
> Monday through Friday in the Morning (AU/Canberra time).
> 
> Things have been crazy busy, so a last set of ext4 backports only
> happened Friday starting around 10pm localtime.  (Yes, I have no
> life.)

Ah, sorry.  I didn't look at the dates carefully.  Thanks for taking
care of this.

It's so weird that kbuild and I didn't send this bug report.  I can't
figure that bit out at all.  It's not super common though and other
people are looking at static analysis so it worked out in the end.

regards,
dan carpenter