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>] [day] [month] [year] [list]
Date:	Thu, 01 Oct 2015 23:01:39 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Lijun Pan <lijunpan2000@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] fsl-ifc: fix compilation error on ARM's 42 bit VA

On Thursday 01 October 2015 10:55:16 Lijun Pan wrote:
> Lijun Pan
> On Oct 1, 2015 3:34 AM, "Arnd Bergmann" <arnd@...db.de> wrote:
> >
> > On Wednesday 30 September 2015 17:55:42 Lijun Pan wrote:
> > > Need to include sched.h to fix the following compilation error
> > > if FSL_IFC is enabled on ARM64 machine.
> >
> > That's good, but you did not change the subject line accordingly.
> >
> 
> I actually add 'ARM's ' in the subject.
> How about I change it to
> fsl-ifc: fix compiler error with ARMv8's 42 bit VA and FSL_IFC enabled
> I assume above subject is longer than 65 characters. Is that OK to you?
> Do you have a better subject in mind?
> 
> Thanks for your kind review.

I think the '42 bit VA' part is what is actually misleading, that
is the part that confused me. From your description it sounds like
the problem is CONFIG_COMPAT being disabled, and that would
also be possible with 39-bit VA. Also, it would be clearer to
mention ARM64 instead of ARM, as from the kernel's perspective
those are two different architectures.

How about simply

fsl-ifc: add missing include on ARM64

that would be sufficient for readers, and they can get the
background from the changelog text. If you want to get more
specific, it could be

fsl-ifc: add missing include on ARM64 without CONFIG_COMPAT

Note that 'missing include' more or less implies a compile error
and better describes /what/ the patch does while the changelog
describes why we do it (the compiler output and why that happened).

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ