linux-kernel - Re: [PATCH] block: Change 'unsigned' to 'unsigned int' throughout block layer

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: <20180215021321.GB30522@ZenIV.linux.org.uk>
Date:   Thu, 15 Feb 2018 02:13:21 +0000
From:   Al Viro <viro@...IV.linux.org.uk>
To:     John Pittman <jpittman@...hat.com>
Cc:     axboe@...nel.dk, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] block: Change 'unsigned' to 'unsigned int' throughout
 block layer

On Wed, Feb 14, 2018 at 08:37:02PM -0500, John Pittman wrote:
> In quite a few files throughout the block layer, the bare 'unsigned' is
> used rather than the preferred 'unsigned int'.

Preferred by whom?

>  The issue was

What is that "issue" and why is it a problem in the first place?

> exposed by checkpatch.pl.  Warnings encountered were:

Oh, good - so presumably it does have some explanations beyond "The Most Holy
checkpatch.pl Spake Unto Us"; could the esteemed sir share those with us?