All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: erhard_f@mailbox.org, jack@suse.cz, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/64s: Fix possible corruption on big endian due to pgd/pud_present()
Date: Sun, 17 Feb 2019 17:23:33 +1100	[thread overview]
Message-ID: <20190217062333.GC31125@350D> (raw)
In-Reply-To: <20190216142206.GE14180@gate.crashing.org>

On Sat, Feb 16, 2019 at 08:22:12AM -0600, Segher Boessenkool wrote:
> Hi all,
> 
> On Sat, Feb 16, 2019 at 09:55:11PM +1100, Balbir Singh wrote:
> > On Thu, Feb 14, 2019 at 05:23:39PM +1100, Michael Ellerman wrote:
> > > In v4.20 we changed our pgd/pud_present() to check for _PAGE_PRESENT
> > > rather than just checking that the value is non-zero, e.g.:
> > > 
> > >   static inline int pgd_present(pgd_t pgd)
> > >   {
> > >  -       return !pgd_none(pgd);
> > >  +       return (pgd_raw(pgd) & cpu_to_be64(_PAGE_PRESENT));
> > >   }
> > > 
> > > Unfortunately this is broken on big endian, as the result of the
> > > bitwise && is truncated to int, which is always zero because
> 
> (Bitwise "&" of course).
> 
> > Not sure why that should happen, why is the result an int? What
> > causes the casting of pgd_t & be64 to be truncated to an int.
> 
> Yes, it's not obvious as written...  It's simply that the return type of
> pgd_present is int.  So it is truncated _after_ the bitwise and.
>

Thanks, I am surprised the compiler does not complain about the truncation
of bits. I wonder if we are missing -Wconversion

Balbir

WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <bsingharora@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	erhard_f@mailbox.org, jack@suse.cz, linuxppc-dev@ozlabs.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/64s: Fix possible corruption on big endian due to pgd/pud_present()
Date: Sun, 17 Feb 2019 17:23:33 +1100	[thread overview]
Message-ID: <20190217062333.GC31125@350D> (raw)
In-Reply-To: <20190216142206.GE14180@gate.crashing.org>

On Sat, Feb 16, 2019 at 08:22:12AM -0600, Segher Boessenkool wrote:
> Hi all,
> 
> On Sat, Feb 16, 2019 at 09:55:11PM +1100, Balbir Singh wrote:
> > On Thu, Feb 14, 2019 at 05:23:39PM +1100, Michael Ellerman wrote:
> > > In v4.20 we changed our pgd/pud_present() to check for _PAGE_PRESENT
> > > rather than just checking that the value is non-zero, e.g.:
> > > 
> > >   static inline int pgd_present(pgd_t pgd)
> > >   {
> > >  -       return !pgd_none(pgd);
> > >  +       return (pgd_raw(pgd) & cpu_to_be64(_PAGE_PRESENT));
> > >   }
> > > 
> > > Unfortunately this is broken on big endian, as the result of the
> > > bitwise && is truncated to int, which is always zero because
> 
> (Bitwise "&" of course).
> 
> > Not sure why that should happen, why is the result an int? What
> > causes the casting of pgd_t & be64 to be truncated to an int.
> 
> Yes, it's not obvious as written...  It's simply that the return type of
> pgd_present is int.  So it is truncated _after_ the bitwise and.
>

Thanks, I am surprised the compiler does not complain about the truncation
of bits. I wonder if we are missing -Wconversion

Balbir


  reply	other threads:[~2019-02-17  6:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  6:23 [PATCH] powerpc/64s: Fix possible corruption on big endian due to pgd/pud_present() Michael Ellerman
2019-02-14  6:23 ` Michael Ellerman
2019-02-14 16:31 ` Jan Kara
2019-02-14 16:31   ` Jan Kara
2019-02-16 10:55 ` Balbir Singh
2019-02-16 10:55   ` Balbir Singh
2019-02-16 14:22   ` Segher Boessenkool
2019-02-16 14:22     ` Segher Boessenkool
2019-02-17  6:23     ` Balbir Singh [this message]
2019-02-17  6:23       ` Balbir Singh
2019-02-17  8:34       ` Michael Ellerman
2019-02-17 21:55         ` Balbir Singh
2019-02-17 21:55           ` Balbir Singh
2019-02-18  0:49           ` Michael Ellerman
2019-02-18  0:49             ` Michael Ellerman
2019-02-19 12:01             ` Balbir Singh
2019-02-19 12:01               ` Balbir Singh
2019-02-19 20:15             ` Segher Boessenkool
2019-02-19 20:15               ` Segher Boessenkool
2019-02-20 11:18               ` Michael Ellerman
2019-02-20 11:18                 ` Michael Ellerman
2019-02-20 14:51                 ` Segher Boessenkool
2019-02-20 14:51                   ` Segher Boessenkool
2019-02-17  8:34     ` Michael Ellerman
2019-02-16 13:15 ` Andreas Schwab
2019-02-16 13:15   ` Andreas Schwab
2019-02-17  8:26   ` Michael Ellerman
2019-02-17  8:26     ` Michael Ellerman
2019-02-17  8:21 ` Michael Ellerman
2019-02-17  8:21   ` Michael Ellerman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190217062333.GC31125@350D \
    --to=bsingharora@gmail.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=erhard_f@mailbox.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.