From: Greg KH <greg@kroah.com>
To: Peter Weber <peter.weber@ttyhoney.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [drm/i915: Do not store the error pointer for a failed userptr registration] Candidate for stable tree?
Date: Mon, 10 Nov 2014 11:56:36 +0900 [thread overview]
Message-ID: <20141110025636.GA29809@kroah.com> (raw)
In-Reply-To: <574931b8edea4d60014d5e9b31daa4a1@ttyhoney.com>
On Fri, Oct 31, 2014 at 04:41:02PM +0100, Peter Weber wrote:
> Hello!
>
> Is the patch[0] mentioned in the subject a possible candidate for the next
> release of the stable kernel, at time of writing "3.17.3"? It looks like,
> this is
> causing serious problems and we are currently discussing this on the
> bugtracker of
> Archlinux[1].
>
> I'm not sure if I'm personally affected. I suffered unexpected freezes
> since 3.17-rc4 on my machine, at least STDIO and STDOUT are frozen. Maybe
> the
> reaction differs based on the kernel options (see changed behaviour
> through
> CONFIG_PREEMPT_VOLUNTARY=y). In my case, I don't see a null pointer in my
> log
> files.
>
> I hope this doesn't offend against the stable kernel rules.
>
> [0]
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e9681366ea9e76ab8f75e84351f2f3ca63ee542c
> # commit id is: e9681366ea9e76ab8f75e84351f2f3ca63ee542c
> # already send to stable@vger.kernel.org, but not included in current
> stable "3.17.2"
> [1] https://bugs.archlinux.org/task/42353
It's now queued up, sorry, the backlog is really long right now :(
prev parent reply other threads:[~2014-11-10 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 15:41 [drm/i915: Do not store the error pointer for a failed userptr registration] Candidate for stable tree? Peter Weber
2014-11-10 2:56 ` Greg KH [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=20141110025636.GA29809@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.weber@ttyhoney.com \
--cc=stable@vger.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.