From: Dan Carpenter <dan.carpenter@oracle.com>
To: Paul Lawrence <paullawrence@google.com>
Cc: devel@driverdev.osuosl.org, "Todd Kjos" <tkjos@android.com>,
"Ben Hutchings" <ben@decadent.org.uk>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Arve Hjønnevåg" <arve@android.com>,
"Martijn Coenen" <maco@android.com>
Subject: Re: [PATCH] staging: android: ashmem: Remove deadlock
Date: Thu, 8 Mar 2018 14:02:44 +0300 [thread overview]
Message-ID: <20180308110244.htlc5uh5aqtltgol@mwanda> (raw)
In-Reply-To: <20180307214042.135109-1-paullawrence@google.com>
Thanks! Somebody already sent this.
On Wed, Mar 07, 2018 at 01:40:30PM -0800, Paul Lawrence wrote:
> Regression introduced in commit ce8a3a9e76d0193e2e8d74a06d275b3c324ca652
> ("staging: android: ashmem: Fix a race condition in pin ioctls")
> causing deadlock.
Use the Fixes tag for this. The format is:
Fixes: ce8a3a9e76d0 ("staging: android: ashmem: Fix a race condition in pin ioctls")
Then you only need one stable CC line. Just the oldest kernel which
needs to be patched.
Cc: <stable@vger.kernel.org> # 3.18.x
The extra git hash after the stable CC is for if a bug requires several
patches to fix it. In this case it only requires just this patch so
there's no need to have the hash.
Basically you did extra work which isn't required. Anyway, this fix was
already merged so no need to resend or anything.
regards,
dan carpenter
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2018-03-08 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 21:40 Paul Lawrence
2018-03-07 21:48 ` Nathan Chancellor
2018-03-07 22:02 ` Paul Lawrence
2018-03-07 22:07 ` Greg Kroah-Hartman
2018-03-07 22:06 ` Paul Lawrence
2018-03-08 11:02 ` Dan Carpenter [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=20180308110244.htlc5uh5aqtltgol@mwanda \
--to=dan.carpenter@oracle.com \
--cc=arve@android.com \
--cc=ben@decadent.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=paullawrence@google.com \
--cc=stable@vger.kernel.org \
--cc=tkjos@android.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
all inboxes | Powered by JetHome®