All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: uaccess: Implement strict user copy checks
Date: Wed, 18 Aug 2010 14:28:44 +0200	[thread overview]
Message-ID: <201008181428.45029.arnd@arndb.de> (raw)
In-Reply-To: <1282094950-6184-1-git-send-email-sboyd@codeaurora.org>

On Wednesday 18 August 2010, Stephen Boyd wrote:
> 
> I'm unsure what needs to be done for the follow up patch. Shouldn't
> it be multiple patches sent to each arch maintainer to fix the
> wording?

No, that will just result in half of them applying it, best make 
a single patch and send it to linux-arch at vger.kernel.org for review.

It's probably best to move the config option to lib/Kconfig.debug
so it only appears once, and make it depend on DEBUG_USER_COPY_CHECKS,
which is then unconditionally defined by the architectures that want it.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH v2] ARM: uaccess: Implement strict user copy checks
Date: Wed, 18 Aug 2010 14:28:44 +0200	[thread overview]
Message-ID: <201008181428.45029.arnd@arndb.de> (raw)
In-Reply-To: <1282094950-6184-1-git-send-email-sboyd@codeaurora.org>

On Wednesday 18 August 2010, Stephen Boyd wrote:
> 
> I'm unsure what needs to be done for the follow up patch. Shouldn't
> it be multiple patches sent to each arch maintainer to fix the
> wording?

No, that will just result in half of them applying it, best make 
a single patch and send it to linux-arch@vger.kernel.org for review.

It's probably best to move the config option to lib/Kconfig.debug
so it only appears once, and make it depend on DEBUG_USER_COPY_CHECKS,
which is then unconditionally defined by the architectures that want it.

	Arnd

  reply	other threads:[~2010-08-18 12:28 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  3:02 [PATCH] ARM: uaccess: Implement strict user copy checks Stephen Boyd
2010-08-04  3:02 ` Stephen Boyd
2010-08-10 22:46 ` Stephen Boyd
2010-08-10 22:46   ` Stephen Boyd
2010-08-10 22:55   ` Russell King - ARM Linux
2010-08-10 22:55     ` Russell King - ARM Linux
2010-08-11  0:27     ` Stephen Boyd
2010-08-11  0:27       ` Stephen Boyd
2010-08-18  1:29       ` [PATCH v2] " Stephen Boyd
2010-08-18  1:29         ` Stephen Boyd
2010-08-18 12:28         ` Arnd Bergmann [this message]
2010-08-18 12:28           ` Arnd Bergmann
2010-08-18 19:48           ` Stephen Boyd
2010-08-18 19:48             ` Stephen Boyd
2010-08-19 11:09             ` Arnd Bergmann
2010-08-19 11:09               ` Arnd Bergmann
2010-08-24 15:06               ` Heiko Carstens
2010-08-24 15:06                 ` Heiko Carstens
2010-08-24 15:26                 ` Arnd Bergmann
2010-08-24 15:26                   ` Arnd Bergmann
2010-08-24 15:47                   ` Heiko Carstens
2010-08-24 15:47                     ` Heiko Carstens
2010-08-25 12:14                     ` Arnd Bergmann
2010-08-25 12:14                       ` Arnd Bergmann
2010-08-25 12:54                       ` Heiko Carstens
2010-08-25 12:54                         ` Heiko Carstens
2010-08-25 13:55                         ` Arnd Bergmann
2010-08-25 13:55                           ` Arnd Bergmann
2010-08-25 14:40                           ` Heiko Carstens
2010-08-25 14:40                             ` Heiko Carstens
2010-08-28  1:35                             ` Stephen Boyd
2010-08-28  1:35                               ` Stephen Boyd
2010-08-28  7:43                               ` Heiko Carstens
2010-08-28  7:43                                 ` Heiko Carstens
2010-08-28  9:56                                 ` Arnd Bergmann
2010-08-28  9:56                                   ` Arnd Bergmann
2010-09-04  4:49                                 ` Stephen Boyd
2010-09-04  4:49                                   ` Stephen Boyd
2010-09-14  3:07                                   ` Stephen Boyd
2010-09-14  3:07                                     ` Stephen Boyd
2010-09-14  8:25                                     ` Heiko Carstens
2010-09-14  8:25                                       ` Heiko Carstens
2010-09-14 13:10                                       ` Arnd Bergmann
2010-09-14 13:10                                         ` Arnd Bergmann
2010-09-14 14:18                                         ` Heiko Carstens
2010-09-14 14:18                                           ` Heiko Carstens
2010-08-19  2:28           ` [PATCHv2 2/1] Consolidate CONFIG_DEBUG_STRICT_USER_COPY_CHECKS Stephen Boyd
2010-08-19  2:28             ` Stephen Boyd
2010-08-19  4:38             ` Arjan van de Ven
2010-08-19  4:38               ` Arjan van de Ven
2010-08-19  4:47             ` Stephen Rothwell
2010-08-19  4:47               ` Stephen Rothwell
2010-08-19 11:04               ` Arnd Bergmann
2010-08-19 11:04                 ` Arnd Bergmann
2010-08-11  3:04 ` [PATCH] ARM: uaccess: Implement strict user copy checks Arnd Bergmann
2010-08-11  3:04   ` Arnd Bergmann
2010-08-11 18:46   ` Stephen Boyd
2010-08-11 18:46     ` Stephen Boyd
2010-08-12 15:00     ` Arnd Bergmann
2010-08-12 15:00       ` Arnd Bergmann

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=201008181428.45029.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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.