* commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable
@ 2015-09-24 8:09 Roland Dreier
2015-09-24 8:51 ` Jan Kara
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Roland Dreier @ 2015-09-24 8:09 UTC (permalink / raw)
To: stable; +Cc: Jan Kara, Theodore Ts'o
Commit 6f6a6fda2945 "jbd2: fix ocfs2 corrupt when updating journal
superblock fails" was tagged for -stable and was picked up by at least
3.10.y etc. However the newer commit 841df7df1962 "jbd2: avoid
infinite loop when destroying aborted journal" fixes a possible hang
caused by that earlier commit, so all stable trees that picked up
6f6a6fda2945 should probably also pick up the fix to it.
- R.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable
2015-09-24 8:09 commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable Roland Dreier
@ 2015-09-24 8:51 ` Jan Kara
2015-09-26 17:55 ` Greg KH
2015-09-25 11:23 ` Jiri Slaby
2015-10-08 22:41 ` Ben Hutchings
2 siblings, 1 reply; 6+ messages in thread
From: Jan Kara @ 2015-09-24 8:51 UTC (permalink / raw)
To: Roland Dreier; +Cc: stable, Jan Kara, Theodore Ts'o
On Thu 24-09-15 01:09:18, Roland Dreier wrote:
> Commit 6f6a6fda2945 "jbd2: fix ocfs2 corrupt when updating journal
> superblock fails" was tagged for -stable and was picked up by at least
> 3.10.y etc. However the newer commit 841df7df1962 "jbd2: avoid
> infinite loop when destroying aborted journal" fixes a possible hang
> caused by that earlier commit, so all stable trees that picked up
> 6f6a6fda2945 should probably also pick up the fix to it.
Right. Thanks for spotting this. I forgot to tag that commit with stable
tag.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable
2015-09-24 8:09 commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable Roland Dreier
2015-09-24 8:51 ` Jan Kara
@ 2015-09-25 11:23 ` Jiri Slaby
2015-10-08 22:41 ` Ben Hutchings
2 siblings, 0 replies; 6+ messages in thread
From: Jiri Slaby @ 2015-09-25 11:23 UTC (permalink / raw)
To: Roland Dreier, stable; +Cc: Jan Kara, Theodore Ts'o
On 09/24/2015, 10:09 AM, Roland Dreier wrote:
> Commit 6f6a6fda2945 "jbd2: fix ocfs2 corrupt when updating journal
> superblock fails" was tagged for -stable and was picked up by at least
> 3.10.y etc. However the newer commit 841df7df1962 "jbd2: avoid
> infinite loop when destroying aborted journal" fixes a possible hang
> caused by that earlier commit, so all stable trees that picked up
> 6f6a6fda2945 should probably also pick up the fix to it.
It does not apply to 3.12 at all :(. Could someone provide a backport?
thanks,
--
js
suse labs
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable
2015-09-24 8:51 ` Jan Kara
@ 2015-09-26 17:55 ` Greg KH
2015-09-28 20:39 ` Jan Kara
0 siblings, 1 reply; 6+ messages in thread
From: Greg KH @ 2015-09-26 17:55 UTC (permalink / raw)
To: Jan Kara; +Cc: Roland Dreier, stable, Jan Kara, Theodore Ts'o
On Thu, Sep 24, 2015 at 10:51:11AM +0200, Jan Kara wrote:
> On Thu 24-09-15 01:09:18, Roland Dreier wrote:
> > Commit 6f6a6fda2945 "jbd2: fix ocfs2 corrupt when updating journal
> > superblock fails" was tagged for -stable and was picked up by at least
> > 3.10.y etc. However the newer commit 841df7df1962 "jbd2: avoid
> > infinite loop when destroying aborted journal" fixes a possible hang
> > caused by that earlier commit, so all stable trees that picked up
> > 6f6a6fda2945 should probably also pick up the fix to it.
>
> Right. Thanks for spotting this. I forgot to tag that commit with stable
> tag.
Thanks, now applied to 4.1 and 4.2, does not backport cleanly to 3.10 or
3.14 :(
greg k-h
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable
2015-09-26 17:55 ` Greg KH
@ 2015-09-28 20:39 ` Jan Kara
0 siblings, 0 replies; 6+ messages in thread
From: Jan Kara @ 2015-09-28 20:39 UTC (permalink / raw)
To: Greg KH; +Cc: Jan Kara, Roland Dreier, stable, Jan Kara, Theodore Ts'o
On Sat 26-09-15 10:55:05, Greg KH wrote:
> On Thu, Sep 24, 2015 at 10:51:11AM +0200, Jan Kara wrote:
> > On Thu 24-09-15 01:09:18, Roland Dreier wrote:
> > > Commit 6f6a6fda2945 "jbd2: fix ocfs2 corrupt when updating journal
> > > superblock fails" was tagged for -stable and was picked up by at least
> > > 3.10.y etc. However the newer commit 841df7df1962 "jbd2: avoid
> > > infinite loop when destroying aborted journal" fixes a possible hang
> > > caused by that earlier commit, so all stable trees that picked up
> > > 6f6a6fda2945 should probably also pick up the fix to it.
> >
> > Right. Thanks for spotting this. I forgot to tag that commit with stable
> > tag.
>
> Thanks, now applied to 4.1 and 4.2, does not backport cleanly to 3.10 or
> 3.14 :(
I'll backport the fix for 3.12 so it'll hopefully work for 3.14 and 3.10 as
well.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable
2015-09-24 8:09 commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable Roland Dreier
2015-09-24 8:51 ` Jan Kara
2015-09-25 11:23 ` Jiri Slaby
@ 2015-10-08 22:41 ` Ben Hutchings
2 siblings, 0 replies; 6+ messages in thread
From: Ben Hutchings @ 2015-10-08 22:41 UTC (permalink / raw)
To: Roland Dreier, stable; +Cc: Jan Kara, Theodore Ts'o
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
On Thu, 2015-09-24 at 01:09 -0700, Roland Dreier wrote:
> Commit 6f6a6fda2945 "jbd2: fix ocfs2 corrupt when updating journal
> superblock fails" was tagged for -stable and was picked up by at least
> 3.10.y etc. However the newer commit 841df7df1962 "jbd2: avoid
> infinite loop when destroying aborted journal" fixes a possible hang
> caused by that earlier commit, so all stable trees that picked up
> 6f6a6fda2945 should probably also pick up the fix to it.
I've queued this up for 3.2, thanks.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-10-08 22:42 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-24 8:09 commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable Roland Dreier
2015-09-24 8:51 ` Jan Kara
2015-09-26 17:55 ` Greg KH
2015-09-28 20:39 ` Jan Kara
2015-09-25 11:23 ` Jiri Slaby
2015-10-08 22:41 ` Ben Hutchings
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.