All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Arve Hjønnevåg" <arve@android.com>
Cc: Greg KH <greg@kroah.com>,
	devel@driverdev.osuosl.org,
	Christopher Lais <chris+android@zenthought.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 1/2] Staging: android: binder: Add some error checks
Date: Wed, 1 Feb 2012 09:53:22 +0300	[thread overview]
Message-ID: <20120201065322.GA24652@mwanda> (raw)
In-Reply-To: <CAMP5XgedsSDtYa-bZCW--+Hj41sN94tDXQ8_d7c4=fT5bJ7mTQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]

On Tue, Jan 31, 2012 at 03:20:30PM -0800, Arve Hjønnevåg wrote:
> 2012/1/31 Greg KH <greg@kroah.com>:
> > On Sat, Jan 21, 2012 at 11:22:08AM +0300, Dan Carpenter wrote:
> >> On Fri, Jan 20, 2012 at 07:56:20PM -0800, Arve Hjønnevåg wrote:
> >> > - Add a mutex to protect against two processes mmapping the
> >> >   same binder_proc.
> >> > - After locking mmap_sem, check that the vma we want to access
> >> >   (still) points to the same mm_struct.
> >> > - Use proc->tsk instead of current to get the files struct since
> >> >   this is where we get the rlimit from.
> >>
> >> This doesn't seem related to the locking change at all.  Probably
> >> this patch should be split into three patches, one bugfix per
> >> patch, unless they are very closely related.
> >
> > I agree.  Arve, is this all fixing one problem, or multiple ones?  If
> > multiple ones, we need this split up into multiple patches.
> >
> 
> That depend on your point of view. It fixes crashes if you use the
> same binder file pointer from multiple processes. It seemed excessive
> to have three patches for this.

It would have helped you to write a better changelog.  The subject
says "[patch] android: grab bag of random fixes" and the the
description matches that.  You have no idea how annoyed I get at
grab bag patches.

Also don't ignore review comments.  I review a lot of staging
patches and I'm not an expert on every driver so my review comments
are often wrong.  I don't get upset when people tell me that.
Review is part of the process.  Everybody does it.

regards,
dan carpenter


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-01  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21  3:56 [PATCH 0/2] Binder bug fixes Arve Hjønnevåg
2012-01-21  3:56 ` [PATCH 1/2] Staging: android: binder: Add some error checks Arve Hjønnevåg
2012-01-21  8:22   ` Dan Carpenter
2012-01-31 18:52     ` Greg KH
2012-01-31 23:20       ` Arve Hjønnevåg
2012-02-01  6:53         ` Dan Carpenter [this message]
2012-02-01 22:29           ` Arve Hjønnevåg
2012-02-01 22:47             ` Greg KH
2012-02-01 23:29               ` [PATCH] Staging: android: binder: Fix crashes when sharing a binder file between processes Arve Hjønnevåg
2012-02-02  6:27               ` [PATCH 1/2] Staging: android: binder: Add some error checks Dan Carpenter
2012-01-21  3:56 ` [PATCH 2/2] Staging: android: binder: Don't call dump_stack in binder_vma_open Arve Hjønnevåg

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=20120201065322.GA24652@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=arve@android.com \
    --cc=chris+android@zenthought.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.