Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753023AbcDVVyL (ORCPT ); Fri, 22 Apr 2016 17:54:11 -0400 Received: from mail-vk0-f52.google.com ([209.85.213.52]:33598 "EHLO mail-vk0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752217AbcDVVyJ (ORCPT ); Fri, 22 Apr 2016 17:54:09 -0400 MIME-Version: 1.0 X-Originating-IP: [2a01:cb1c:13e:de00:2ed0:5aff:fe00:9f21] In-Reply-To: <20160418230601.GA18496@dastard> References: <20160415021737.GZ567@dastard> <5714FB36.6020704@sandeen.net> <20160418230601.GA18496@dastard> From: Florian Margaine Date: Fri, 22 Apr 2016 23:53:48 +0200 Message-ID: Subject: Re: [PATCH] fs: add the FIGETFROZEN ioctl call To: Dave Chinner Cc: Eric Sandeen , Alexander Viro , Jeff Layton , "J. Bruce Fields" , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 707 Lines: 24 On Tue, Apr 19, 2016 at 1:06 AM, Dave Chinner 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@fromorbit.com Regards, Florian