public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Oleg Nesterov <oleg@tv-sign.ru>,
	vatsa@in.ibm.com, Gautham R Shenoy <ego@in.ibm.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	LKML <linux-kernel@vger.kernel.org>, David Chinner <dgc@sgi.com>,
	Nigel Cunningham <ncunningham@linuxmail.org>
Subject: Re: [PATCH] Make XFS workqueues nonfreezable
Date: Thu, 1 Mar 2007 01:25:54 -0800	[thread overview]
Message-ID: <20070301012554.8426b5cb.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070301091521.GA20171@elf.ucw.cz>

On Thu, 1 Mar 2007 10:15:21 +0100 Pavel Machek <pavel@ucw.cz> wrote:

> > > -	xfslogd_workqueue = create_freezeable_workqueue("xfslogd");
> > > +	xfslogd_workqueue = create_workqueue("xfslogd");
> > >  	if (!xfslogd_workqueue)
> > >  		goto out_free_buf_zone;
> > >  
> > > -	xfsdatad_workqueue = create_freezeable_workqueue("xfsdatad");
> > > +	xfsdatad_workqueue = create_workqueue("xfsdatad");
> > >  	if (!xfsdatad_workqueue)
> > >  		goto out_destroy_xfslogd_workqueue;
> > >  
> > 
> > Won't this break suspend+XFS?
> > 
> > If so, and given that nobody seems to be reporting this deadlock, perhaps
> > we'd be better off leaving things as-is for the while?
> 
> Worst case is not breaking suspend+XFS, worst case is XFS writing to
> disk after freeze(), leading to subtle fs corruption.
> 
> (But noone could reproduce corruption before, and I was told XFS will
> not do those writes these days).

hm, OK.   To avoid making a decision I sent the patch to David ;)

  reply	other threads:[~2007-03-01  9:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 21:51 Problem with freezable workqueues Rafael J. Wysocki
2007-02-27 23:28 ` Oleg Nesterov
2007-02-27 23:36   ` Johannes Berg
2007-02-28  0:00     ` Rafael J. Wysocki
2007-02-28  0:00       ` Johannes Berg
2007-02-28 18:06     ` Gautham R Shenoy
2007-02-27 23:57   ` Rafael J. Wysocki
2007-02-28  0:01     ` Johannes Berg
2007-02-28  0:08       ` Rafael J. Wysocki
2007-02-28  1:14         ` Nigel Cunningham
2007-02-28 10:59           ` Rafael J. Wysocki
2007-02-28 20:36           ` Johannes Berg
2007-02-28  3:07     ` Srivatsa Vaddagiri
2007-02-28  8:48       ` Oleg Nesterov
2007-02-28  9:10         ` Srivatsa Vaddagiri
2007-02-28  9:43           ` Oleg Nesterov
2007-02-28 11:09           ` Rafael J. Wysocki
2007-02-28 18:17       ` Gautham R Shenoy
2007-02-28 18:41         ` Rafael J. Wysocki
2007-02-28  8:54     ` Pavel Machek
2007-02-28  3:01 ` Srivatsa Vaddagiri
2007-02-28  3:51   ` Srivatsa Vaddagiri
2007-02-28 11:11     ` Rafael J. Wysocki
2007-02-28 13:17       ` Srivatsa Vaddagiri
2007-02-28 13:27         ` Srivatsa Vaddagiri
2007-02-28 17:41           ` Rafael J. Wysocki
2007-02-28 17:40         ` Rafael J. Wysocki
2007-02-28 19:17         ` Rafael J. Wysocki
2007-02-28 19:32           ` Oleg Nesterov
2007-02-28 19:43             ` Rafael J. Wysocki
2007-02-28 20:08               ` Oleg Nesterov
2007-02-28 20:25                 ` Rafael J. Wysocki
2007-02-28 20:35                   ` Oleg Nesterov
2007-02-28 22:39                     ` Rafael J. Wysocki
2007-02-28 22:44                       ` Pavel Machek
2007-02-28 23:54                         ` [PATCH] Make XFS workqueues nonfreezable Rafael J. Wysocki
2007-03-01  8:03                           ` Andrew Morton
2007-03-01  9:15                             ` Pavel Machek
2007-03-01  9:25                               ` Andrew Morton [this message]
2007-02-28 21:16                   ` Problem with freezable workqueues Pavel Machek
2007-03-06  0:30 ` Johannes Berg
2007-03-06 20:31   ` Rafael J. Wysocki
2007-03-06 22:25     ` Nigel Cunningham
2007-03-06 22:57       ` Rafael J. Wysocki
2007-03-07 23:10     ` Johannes Berg

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=20070301012554.8426b5cb.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dgc@sgi.com \
    --cc=ego@in.ibm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.org \
    --cc=oleg@tv-sign.ru \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=vatsa@in.ibm.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