All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Robert Love <rlove@google.com>
Cc: Shankar Brahadeeswaran <shankoo77@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Bjorn Bringert <bringert@google.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	devel@driverdev.osuosl.org, Hugh Dickins <hughd@google.com>,
	Anjana V Kumar <anjanavk12@gmail.com>
Subject: Re: [BUG] staging: android: ashmem: Deadlock during ashmem_shrink
Date: Tue, 30 Apr 2013 16:33:34 -0700	[thread overview]
Message-ID: <20130430233334.GA32383@kroah.com> (raw)
In-Reply-To: <CAG6tG3ybiaSRt15s63Dz_33_-jsrrBAamOAV_t7QOW0N_zWueg@mail.gmail.com>

On Tue, Apr 30, 2013 at 06:32:54PM -0400, Robert Love wrote:
> > After this experiment, I too think that this patch (returning from
> > ashmem_shrink if the lock is not available) is good enough and does
> > not seem to have any major side effects.
> >
> > PS: Any plans of submitting this patch formally?
> 
> Sure. Greg? :)

I'll be glad to take it if you resend it in a format that I can apply it
in :)

thanks,

greg k-h

      reply	other threads:[~2013-04-30 23:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJsYZ5kk=J_Sc7w5dbMbkWWv8dXEU0ojKjEKNqH=Q6Tf2f7mQg@mail.gmail.com>
2013-04-22 14:22 ` [BUG] staging: android: ashmem: Deadlock during ashmem_shrink Dan Carpenter
2013-04-22 14:43   ` Robert Love
2013-04-23 16:20     ` Shankar Brahadeeswaran
2013-04-23 17:24       ` Robert Love
2013-04-25 13:54         ` Shankar Brahadeeswaran
2013-04-25 14:13           ` Shankar Brahadeeswaran
2013-04-25 15:05           ` Robert Love
2013-04-30 13:29             ` Shankar Brahadeeswaran
2013-04-30 22:32               ` Robert Love
2013-04-30 23:33                 ` Greg Kroah-Hartman [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=20130430233334.GA32383@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=anjanavk12@gmail.com \
    --cc=bringert@google.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlove@google.com \
    --cc=shankoo77@gmail.com \
    --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.