All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Oleg Nesterov <oleg@redhat.com>,
	lvc-project@linuxtesting.org
Subject: Re: [PATCH] arm64: ptrace: user_regset_copyin_ignore() always returns 0
Date: Thu, 29 Sep 2022 18:11:31 +0100	[thread overview]
Message-ID: <YzXRw3l9xA+dSY7y@arm.com> (raw)
In-Reply-To: <a93b0e12-7012-7314-4bbb-02a42f7f4b1d@omp.ru>

On Tue, Sep 27, 2022 at 09:46:11PM +0300, Sergey Shtylyov wrote:
> On 9/26/22 5:01 PM, Catalin Marinas wrote:
> >>>> user_regset_copyin_ignore() always return 0, so checking its result seems
> >>>> pointless -- don't do this...
[...]
> >>> I think it would be better to have user_regset_copyin_ignore() return void
> >>> so that we don't run the risk of missing an error code if it starts
> >>> returning one in future.
> >>
> >>    That's the plan! But I need to convert the users 1st, right?
> > 
> > Right, though normally we'd like to see the full series that does the
> > arch clean-up followed by the user_regset_copyin_ignore() return changed
> > to void. If for some reason the last patch is rejected by the maintainer
> > because there are plans to actually return some non-zero value, we'd
> > have to revert the above.
> 
>    Hm... I usually try to avoid a cross-tree patch series but here I should
> be able to use the linux-next repo as I series' base. Is that OK?

It depends on how you plan to merge it, though basing the series off
linux-next is not ideal. It's fine to merge individual patches in one
release though specific trees and the final patch in another but when
you posted this single patch we didn't have the context. So ideally I'd
like to see an ack on the patch converting user_regset_copyin_ignore()
to void. It wasn't obvious there's such patch.

You can also have a cross-tree series and convince one of the maintainer
to pick it up (usually cc'ing akpm does the trick ;)).

-- 
Catalin

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

      reply	other threads:[~2022-09-29 17:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 20:54 [PATCH] arm64: ptrace: user_regset_copyin_ignore() always returns 0 Sergey Shtylyov
2022-09-21  8:56 ` Sergey Shtylyov
2022-09-22 11:59 ` Will Deacon
2022-09-22 17:37   ` Sergey Shtylyov
2022-09-26 14:01     ` Catalin Marinas
2022-09-27 18:46       ` Sergey Shtylyov
2022-09-29 17:11         ` Catalin Marinas [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=YzXRw3l9xA+dSY7y@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=oleg@redhat.com \
    --cc=s.shtylyov@omp.ru \
    --cc=will@kernel.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.