[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171003202731.GG2294@wotan.suse.de>
Date: Tue, 3 Oct 2017 22:27:31 +0200
From: "Luis R. Rodriguez" <mcgrof@...nel.org>
To: Bart Van Assche <Bart.VanAssche@....com>
Cc: "jikos@...nel.org" <jikos@...nel.org>,
"boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>,
"ONeukum@...e.com" <ONeukum@...e.com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"nborisov@...e.com" <nborisov@...e.com>,
"oleg.b.antonyan@...il.com" <oleg.b.antonyan@...il.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>,
"pavel@....cz" <pavel@....cz>,
"darrick.wong@...cle.com" <darrick.wong@...cle.com>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"ming.lei@...hat.com" <ming.lei@...hat.com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"jgross@...e.com" <jgross@...e.com>,
"oleksandr@...alenko.name" <oleksandr@...alenko.name>,
"todd.e.brandt@...ux.intel.com" <todd.e.brandt@...ux.intel.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"mcgrof@...nel.org" <mcgrof@...nel.org>,
"len.brown@...el.com" <len.brown@...el.com>,
"tytso@....edu" <tytso@....edu>, "jack@...e.cz" <jack@...e.cz>
Subject: Re: [RFC 5/5] pm: remove kernel thread freezing
On Tue, Oct 03, 2017 at 08:21:42PM +0000, Bart Van Assche wrote:
> On Tue, 2017-10-03 at 22:17 +0200, Jiri Kosina wrote:
> > On Tue, 3 Oct 2017, Bart Van Assche wrote:
> > > What about the many drivers outside filesystems that use the
> > > set_freezable() / try_to_freeze() / wait_event_freezable() API?
> >
> > Many/most of them are just completely bogus and pointless. I've killed a
> > lot of those in the past, but the copy/paste programming is just too
> > strong enemy to fight against.
>
> If just a single driver would use that API to prevent that I/O occurs while
> processes are frozen then this patch will break that driver.
Yes! And although as Jiri points out, its debatable where this is being used,
but as you suggest there may be *valid* reasons for it *now* even though
originally it *may* have been bogus...
Its why I believe this now can only be done piecemeal wise, slowly but steady.
To avoid regressions, and make this effort bisectable.
Luis
Powered by blists - more mailing lists