[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABRjmp8JHbwELYy-waaz_Tt7um0wyMjWVTcCvSa-4BjTmqk5qQ@mail.gmail.com>
Date: Fri, 22 Apr 2016 23:53:48 +0200
From: Florian Margaine <florian@...gaine.com>
To: Dave Chinner <david@...morbit.com>
Cc: Eric Sandeen <sandeen@...deen.net>,
Alexander Viro <viro@...iv.linux.org.uk>,
Jeff Layton <jlayton@...chiereds.net>,
"J. Bruce Fields" <bfields@...ldses.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fs: add the FIGETFROZEN ioctl call
On Tue, Apr 19, 2016 at 1:06 AM, Dave Chinner <david@...morbit.com> wrote:
>> A way to query freeze state might be nice, I think, but yeah, it's
>> racy, so you can't depend on it - but it might be useful in the "huh,
>> IO is failing, what's going on? Oh, it's frozen, ok" scenario...
>
> So maybe we should just add the frozen state to /proc/self/mountinfo
> or something similar, then people who think it matters can shoot
> themselves in the foot all they want without us needing to care
> about it.
Sorry if it's a basic question, but what is the difference between
/proc/self/mountinfo and providing an ioctl call?
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@...morbit.com
Regards,
Florian
Powered by blists - more mailing lists