All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Atish Patra <Atish.Patra@wdc.com>
Cc: "alex\@ghiti.fr" <alex@ghiti.fr>,
	"aou\@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"keescook\@chromium.org" <keescook@chromium.org>,
	"jhogan\@kernel.org" <jhogan@kernel.org>,
	"catalin.marinas\@arm.com" <catalin.marinas@arm.com>,
	"palmer\@sifive.com" <palmer@sifive.com>,
	"will.deacon\@arm.com" <will.deacon@arm.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ralf\@linux-mips.org" <ralf@linux-mips.org>,
	"linux\@armlinux.org.uk" <linux@armlinux.org.uk>,
	"linux-mm\@kvack.org" <linux-mm@kvack.org>,
	"paul.burton\@mips.com" <paul.burton@mips.com>,
	"linux-riscv\@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"viro\@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"paul.walmsley\@sifive.com" <paul.walmsley@sifive.com>,
	"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
	"hch\@lst.de" <hch@lst.de>,
	linux-arm-kernel@lists.infr
Subject: Re: [PATCH v6 14/14] riscv: Make mmap allocation top-down by default
Date: Tue, 15 Oct 2019 09:48:40 +0200	[thread overview]
Message-ID: <mvmv9sqfnzb.fsf@suse.de> (raw)
In-Reply-To: <d27c8eac16d1cc4d5ca139802b4d0cdd2dbbca11.camel@wdc.com> (Atish Patra's message of "Tue, 15 Oct 2019 00:31:37 +0000")

On Okt 15 2019, Atish Patra <Atish.Patra@wdc.com> wrote:

> Nope. This is only reproducible in RISC-V Fedora Gnome desktop image on
> a HiFive Unleashed + Microsemi Expansion. Just to clarify, there is no
> issue with OpenEmbedded disk image related to memory layout. It was a
> userspace thing.

Does it also happen with any of the openSUSE images?

https://download.opensuse.org/ports/riscv/tumbleweed/images/

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Atish Patra <Atish.Patra@wdc.com>
Cc: linux-arm-kernel@lists.infr,
	"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"alex@ghiti.fr" <alex@ghiti.fr>,
	"jhogan@kernel.org" <jhogan@kernel.org>,
	"palmer@sifive.com" <palmer@sifive.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"paul.burton@mips.com" <paul.burton@mips.com>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>, "hch@lst.de" <hch@lst.de>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH v6 14/14] riscv: Make mmap allocation top-down by default
Date: Tue, 15 Oct 2019 09:48:40 +0200	[thread overview]
Message-ID: <mvmv9sqfnzb.fsf@suse.de> (raw)
In-Reply-To: <d27c8eac16d1cc4d5ca139802b4d0cdd2dbbca11.camel@wdc.com> (Atish Patra's message of "Tue, 15 Oct 2019 00:31:37 +0000")

On Okt 15 2019, Atish Patra <Atish.Patra@wdc.com> wrote:

> Nope. This is only reproducible in RISC-V Fedora Gnome desktop image on
> a HiFive Unleashed + Microsemi Expansion. Just to clarify, there is no
> issue with OpenEmbedded disk image related to memory layout. It was a
> userspace thing.

Does it also happen with any of the openSUSE images?

https://download.opensuse.org/ports/riscv/tumbleweed/images/

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-10-15  7:48 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  6:17 [PATCH v6 00/14] Provide generic top-down mmap layout functions Alexandre Ghiti
2019-08-08  6:17 ` Alexandre Ghiti
2019-08-08  6:17 ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 01/14] mm, fs: Move randomize_stack_top from fs to mm Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 02/14] arm64: Make use of is_compat_task instead of hardcoding this test Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 03/14] arm64: Consider stack randomization for mmap base only when necessary Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 04/14] arm64, mm: Move generic mmap layout functions to mm Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 05/14] arm64, mm: Make randomization selected by generic topdown mmap layout Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 06/14] arm: Properly account for stack randomization and stack guard gap Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 07/14] arm: Use STACK_TOP when computing mmap base address Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 08/14] arm: Use generic mmap top-down layout and brk randomization Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 09/14] mips: Properly account for stack randomization and stack guard gap Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  9:16   ` Sergei Shtylyov
2019-08-08  9:16     ` Sergei Shtylyov
2019-08-08  9:16     ` Sergei Shtylyov
2019-08-09  9:44     ` Alexandre Ghiti
2019-08-09  9:44       ` Alexandre Ghiti
2019-08-09  9:44       ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 10/14] mips: Use STACK_TOP when computing mmap base address Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 11/14] mips: Adjust brk randomization offset to fit generic version Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  9:19   ` Sergei Shtylyov
2019-08-08  9:19     ` Sergei Shtylyov
2019-08-08  9:19     ` Sergei Shtylyov
2019-08-09  9:45     ` Alexandre Ghiti
2019-08-09  9:45       ` Alexandre Ghiti
2019-08-09  9:45       ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 12/14] mips: Replace arch specific way to determine 32bit task with " Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 13/14] mips: Use generic mmap top-down layout and brk randomization Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17 ` [PATCH v6 14/14] riscv: Make mmap allocation top-down by default Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-08-08  6:17   ` Alexandre Ghiti
2019-10-05  2:12   ` Atish Patra
2019-10-05  2:12     ` Atish Patra
2019-10-05  2:12     ` Atish Patra
2019-10-05  2:12     ` Atish Patra
2019-10-07  9:11     ` Alex Ghiti
2019-10-07  9:11       ` Alex Ghiti
2019-10-07  9:11       ` Alex Ghiti
2019-10-07  9:11       ` Alex Ghiti
2019-10-08  0:46       ` Atish Patra
2019-10-08  0:46         ` Atish Patra
2019-10-08  0:46         ` Atish Patra
2019-10-08  0:46         ` Atish Patra
2019-10-08 11:58         ` Alex Ghiti
2019-10-08 11:58           ` Alex Ghiti
2019-10-08 11:58           ` Alex Ghiti
2019-10-08 11:58           ` Alex Ghiti
2019-10-09  2:07           ` Atish Patra
2019-10-09  2:07             ` Atish Patra
2019-10-09  2:07             ` Atish Patra
2019-10-09  2:07             ` Atish Patra
2019-10-09 18:39             ` Alex Ghiti
2019-10-09 18:39               ` Alex Ghiti
2019-10-09 18:39               ` Alex Ghiti
2019-10-09 18:39               ` Alex Ghiti
2019-10-15  0:31               ` Atish Patra
2019-10-15  0:31                 ` Atish Patra
2019-10-15  0:31                 ` Atish Patra
2019-10-15  0:31                 ` Atish Patra
2019-10-15  7:48                 ` Andreas Schwab [this message]
2019-10-15  7:48                   ` Andreas Schwab
2019-10-15  7:48                   ` Andreas Schwab
2019-10-08  9:19       ` Alex Ghiti
2019-10-08  9:19         ` Alex Ghiti
2019-10-08  9:19         ` Alex Ghiti
2019-10-08  9:19         ` Alex Ghiti

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=mvmv9sqfnzb.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=Atish.Patra@wdc.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=catalin.marinas@arm.com \
    --cc=hch@lst.de \
    --cc=jhogan@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infr \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=palmer@sifive.com \
    --cc=paul.burton@mips.com \
    --cc=paul.walmsley@sifive.com \
    --cc=ralf@linux-mips.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will.deacon@arm.com \
    /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.