stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: stable@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Dan Streetman <ddstreet@canonical.com>
Subject: Re: [PATCH stable v5.4+] s390/ptrace: return -ENOSYS when invalid syscall is supplied
Date: Sat, 24 Apr 2021 16:50:41 +0200	[thread overview]
Message-ID: <YIQwQSUDnZJVb0ei@kroah.com> (raw)
In-Reply-To: <20210421165853.148822-1-krzysztof.kozlowski@canonical.com>

On Wed, Apr 21, 2021 at 06:58:53PM +0200, Krzysztof Kozlowski wrote:
> From: Sven Schnelle <svens@linux.ibm.com>
> 
> commit cd29fa798001075a554b978df3a64e6656c25794 upstream.
> 
> The current code returns the syscall number which an invalid
> syscall number is supplied and tracing is enabled. This makes
> the strace testsuite fail.
> 
> Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
> Signed-off-by: Dan Streetman <ddstreet@canonical.com>
> Link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895132
> [krzysztof: adjusted the backport around missing ifdef CONFIG_SECCOMP,
>  add Link and Fixes; apparently this should go with the referenced commit]
> Fixes: 00332c16b160 ("s390/ptrace: pass invalid syscall numbers to tracing")
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>

Thanks for this, now queued up.

greg k-h

      reply	other threads:[~2021-04-24 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 16:58 [PATCH stable v5.4+] s390/ptrace: return -ENOSYS when invalid syscall is supplied Krzysztof Kozlowski
2021-04-24 14:50 ` Greg KH [this message]

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=YIQwQSUDnZJVb0ei@kroah.com \
    --to=greg@kroah.com \
    --cc=ddstreet@canonical.com \
    --cc=gor@linux.ibm.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=stable@vger.kernel.org \
    --cc=svens@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).