From: Greg KH <greg@kroah.com>
To: Coly Li <colyli@suse.de>
Cc: Kent Overstreet <kent.overstreet@gmail.com>, stable@vger.kernel.org
Subject: Re: [PATCH] bcache: Make gc wakeup sane, remove set_task_state()
Date: Mon, 20 Feb 2017 16:19:43 +0100 [thread overview]
Message-ID: <20170220151943.GA9530@kroah.com> (raw)
In-Reply-To: <9d02d389-c432-bddb-f592-018db38372c7@suse.de>
On Mon, Feb 20, 2017 at 10:36:13PM +0800, Coly Li wrote:
> On 2017/2/20 下午10:06, Greg KH wrote:
> > On Mon, Feb 20, 2017 at 04:12:58AM -0900, Kent Overstreet wrote:
> >> On Mon, Feb 20, 2017 at 01:31:37PM +0100, Greg KH wrote:
> >>> On Mon, Jan 23, 2017 at 03:54:07PM +0100, Greg KH wrote:
> >>>> Kent, any hints?
> >>>
> >>> Without a response from the maintainer, I can't apply this...
> >>>
> >>> greg k-h
> >>
> >> Sorry I missed this - yes, this patch should be safe to apply and it does fix
> >> that crash. The relevant code hasn't been changed in ages, 4.4 is definitely
> >> fine.
> >
> > Ok, I've queued this up for 4.9, but for 4.4 it does not apply. Coly,
> > can you provide a working backport for 4.4-stable?
>
> Greg,
>
> It is because the 'commit 29e6c57cc78e ("bcache: bch_gc_thread() is not
> freezable")' remove a "try_to_freeze()" in bch_gc_thread(), which
> happens in v4.7.
>
> I just rebase Kent's fix to v4.4 kernel, solve the conflict. Could you
> please check and try the attached patch ?
That worked, thanks!
greg k-h
prev parent reply other threads:[~2017-02-20 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 13:20 [PATCH] bcache: Make gc wakeup sane, remove set_task_state() colyli
2017-01-23 14:16 ` Greg KH
2017-01-23 14:45 ` Coly Li
2017-01-23 14:54 ` Greg KH
2017-02-20 12:31 ` Greg KH
2017-02-20 13:12 ` Kent Overstreet
2017-02-20 14:06 ` Greg KH
2017-02-20 14:36 ` Coly Li
2017-02-20 15:19 ` 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=20170220151943.GA9530@kroah.com \
--to=greg@kroah.com \
--cc=colyli@suse.de \
--cc=kent.overstreet@gmail.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.