mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: torvalds@linux-foundation.org
Cc: dinguyen@kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] NIOS2: fixes for v6.0
Date: Tue, 16 Aug 2022 09:45:39 -0500	[thread overview]
Message-ID: <20220816144539.371752-1-dinguyen@kernel.org> (raw)

Hi Linus,

Please pull these fixes for NIOS2 for v6.0.

Thanks,

Dinh

The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:

  Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/nios2_fixes_v6.0

for you to fetch changes up to fd0c153daad135d0ec1a53c5dbe6936a724d6ae1:

  nios2: add force_successful_syscall_return() (2022-08-15 11:25:32 -0500)

----------------------------------------------------------------
NIOS2 fixes for v6.0
- Security fixes from Al Viro

----------------------------------------------------------------
Al Viro (6):
      nios2: page fault et.al. are *not* restartable syscalls...
      nios2: don't leave NULLs in sys_call_table[]
      nios2: traced syscall does need to check the syscall number
      nios2: fix syscall restart checks
      nios2: restarts apply only to the first sigframe we build...
      nios2: add force_successful_syscall_return()

 arch/nios2/include/asm/entry.h    |  3 ++-
 arch/nios2/include/asm/ptrace.h   |  2 ++
 arch/nios2/kernel/entry.S         | 22 +++++++++++++++-------
 arch/nios2/kernel/signal.c        |  3 ++-
 arch/nios2/kernel/syscall_table.c |  1 +
 5 files changed, 22 insertions(+), 9 deletions(-)

             reply	other threads:[~2022-08-16 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 14:45 Dinh Nguyen [this message]
2022-08-16 19:21 ` 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=20220816144539.371752-1-dinguyen@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=linux-kernel@vger.kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®