linux-kernel - Re: [PATCH -next] mm/hugetlb.c: fix printk format warning for 32-bit phys_addr

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] [day] [month] [year] [list]

Message-ID: <933c893a29b6c5aa85758ca6a7e2d2c99170bc11.camel@perches.com>
Date:   Thu, 19 Mar 2020 18:06:38 -0700
From:   Joe Perches <joe@...ches.com>
To:     Randy Dunlap <rdunlap@...radead.org>,
        Linux MM <linux-mm@...ck.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] mm/hugetlb.c: fix printk format warning for
 32-bit phys_addr_t

On Thu, 2020-03-19 at 18:03 -0700, Randy Dunlap wrote:
> On 3/18/20 7:37 PM, Joe Perches wrote:
> > On Wed, 2020-03-18 at 19:11 -0700, Randy Dunlap wrote:

> > > I'm fairly sure that the [begin, end) notation is done on purpose, meaning
> > > 
> > > <begin> is included in the range and <end> is not included in the range.
> > 
> > OK, that seems a pretty obscure and not obvious use of
> > interval notation, at least to me. (18 uses treewide ?)
> > 
> > Maybe it could be documented somewhere?
> 
> I thought about where to put that and came up empty.

No worries then, it's likely not _too_ obscure
to anyone that's sent a log for analysis.