From: Palmer Dabbelt <palmer@dabbelt.com> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] RISC-V Fixes for 5.13-rc3 Date: Sat, 24 Jul 2021 13:44:53 -0700 (PDT) [thread overview] Message-ID: <mhng-3e77f70c-4c2d-416f-8d07-3fffd2a23aa4@palmerdabbelt-glaptop> (raw) In-Reply-To: <mhng-5cd676be-7ed7-48de-b740-0e809ae67a56@palmerdabbelt-glaptop> On Sat, 24 Jul 2021 13:44:02 PDT (-0700), Palmer Dabbelt wrote: > The following changes since commit e73f0f0ee7541171d89f2e2491130c7771ba58d3: > > Linux 5.14-rc1 (2021-07-11 15:07:40 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.14-rc3 > > for you to fetch changes up to ea196c548c0ac407afd31d142712b6da8bd00244: > > riscv: __asm_copy_to-from_user: Fix: Typos in comments (2021-07-23 17:49:12 -0700) > > ---------------------------------------------------------------- > RISC-V Fixes for 5.13-rc3 Oops, that should be 5.14-rc3. The tag name is right. > > * A fix to properly set the memory size, which fixes 32-bit systems. > * A fix to allow the initrd to load anywhere in memory, rather that > restricting it to the first 256MiB. > * A fix for the mem= parameter on 64-bit systems, to properly account > for the maximum supported memory now that the kernel is outside the > linear map. > * A fix to avoid installing mappings into the last 4KiB of memory, which > conflicts with error values. > * A fix to avoid the stack from being freed while it is being walked. > * A handful of fixes to the new copy to/from user routines. > --- > There is one particularly odd bit in the history here: the fix for the 32-bit > boot failure is based on an older release, because a recent feature addition > also fixed the bug. I wanted to take that patch so it could be backported to > stable, but it's erased by its own merge. Not sure if there's a better way to > do this, but I figured this was saner than reverting the feature and then > bringing it back. > > ---------------------------------------------------------------- > Akira Tsukamoto (4): > riscv: __asm_copy_to-from_user: Fix: overrun copy > riscv: __asm_copy_to-from_user: Fix: fail on RV32 > riscv: __asm_copy_to-from_user: Remove unnecessary size check > riscv: __asm_copy_to-from_user: Fix: Typos in comments > > Alexandre Ghiti (3): > riscv: Fix memory_limit for 64-bit kernel > riscv: Make sure the linear mapping does not use the kernel mapping > riscv: Make sure the kernel mapping does not overlap with IS_ERR_VALUE > > Bin Meng (1): > riscv: Fix 32-bit RISC-V boot failure > > Heinrich Schuchardt (1): > RISC-V: load initrd wherever it fits into memory > > Jisheng Zhang (1): > riscv: stacktrace: pin the task's stack in get_wchan > > Palmer Dabbelt (1): > Merge remote-tracking branch 'riscv/riscv-fix-32bit' into fixes > > arch/riscv/include/asm/efi.h | 4 ++-- > arch/riscv/kernel/stacktrace.c | 6 +++++- > arch/riscv/lib/uaccess.S | 27 +++++++++++++-------------- > arch/riscv/mm/init.c | 32 ++++++++++++++++++++++++++++---- > 4 files changed, 48 insertions(+), 21 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@dabbelt.com> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] RISC-V Fixes for 5.13-rc3 Date: Sat, 24 Jul 2021 13:44:53 -0700 (PDT) [thread overview] Message-ID: <mhng-3e77f70c-4c2d-416f-8d07-3fffd2a23aa4@palmerdabbelt-glaptop> (raw) In-Reply-To: <mhng-5cd676be-7ed7-48de-b740-0e809ae67a56@palmerdabbelt-glaptop> On Sat, 24 Jul 2021 13:44:02 PDT (-0700), Palmer Dabbelt wrote: > The following changes since commit e73f0f0ee7541171d89f2e2491130c7771ba58d3: > > Linux 5.14-rc1 (2021-07-11 15:07:40 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.14-rc3 > > for you to fetch changes up to ea196c548c0ac407afd31d142712b6da8bd00244: > > riscv: __asm_copy_to-from_user: Fix: Typos in comments (2021-07-23 17:49:12 -0700) > > ---------------------------------------------------------------- > RISC-V Fixes for 5.13-rc3 Oops, that should be 5.14-rc3. The tag name is right. > > * A fix to properly set the memory size, which fixes 32-bit systems. > * A fix to allow the initrd to load anywhere in memory, rather that > restricting it to the first 256MiB. > * A fix for the mem= parameter on 64-bit systems, to properly account > for the maximum supported memory now that the kernel is outside the > linear map. > * A fix to avoid installing mappings into the last 4KiB of memory, which > conflicts with error values. > * A fix to avoid the stack from being freed while it is being walked. > * A handful of fixes to the new copy to/from user routines. > --- > There is one particularly odd bit in the history here: the fix for the 32-bit > boot failure is based on an older release, because a recent feature addition > also fixed the bug. I wanted to take that patch so it could be backported to > stable, but it's erased by its own merge. Not sure if there's a better way to > do this, but I figured this was saner than reverting the feature and then > bringing it back. > > ---------------------------------------------------------------- > Akira Tsukamoto (4): > riscv: __asm_copy_to-from_user: Fix: overrun copy > riscv: __asm_copy_to-from_user: Fix: fail on RV32 > riscv: __asm_copy_to-from_user: Remove unnecessary size check > riscv: __asm_copy_to-from_user: Fix: Typos in comments > > Alexandre Ghiti (3): > riscv: Fix memory_limit for 64-bit kernel > riscv: Make sure the linear mapping does not use the kernel mapping > riscv: Make sure the kernel mapping does not overlap with IS_ERR_VALUE > > Bin Meng (1): > riscv: Fix 32-bit RISC-V boot failure > > Heinrich Schuchardt (1): > RISC-V: load initrd wherever it fits into memory > > Jisheng Zhang (1): > riscv: stacktrace: pin the task's stack in get_wchan > > Palmer Dabbelt (1): > Merge remote-tracking branch 'riscv/riscv-fix-32bit' into fixes > > arch/riscv/include/asm/efi.h | 4 ++-- > arch/riscv/kernel/stacktrace.c | 6 +++++- > arch/riscv/lib/uaccess.S | 27 +++++++++++++-------------- > arch/riscv/mm/init.c | 32 ++++++++++++++++++++++++++++---- > 4 files changed, 48 insertions(+), 21 deletions(-) _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-07-24 20:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-24 20:44 [GIT PULL] RISC-V Fixes for 5.13-rc3 Palmer Dabbelt 2021-07-24 20:44 ` Palmer Dabbelt 2021-07-24 20:44 ` Palmer Dabbelt [this message] 2021-07-24 20:44 ` Palmer Dabbelt 2021-07-24 22:36 ` pr-tracker-bot 2021-07-24 22:36 ` pr-tracker-bot
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=mhng-3e77f70c-4c2d-416f-8d07-3fffd2a23aa4@palmerdabbelt-glaptop \ --to=palmer@dabbelt.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=torvalds@linux-foundation.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: linkBe 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.