From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyrill Gorcunov Subject: Re: [patch 25/26] mount options: fix udf Date: Fri, 25 Jan 2008 16:41:58 +0300 Message-ID: <20080125134158.GA7233@cvg> References: <20080124193341.166753833@szeredi.hu> <20080124193456.220272889@szeredi.hu> <20080124202034.GC6724@cvg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, jack@suse.cz To: Miklos Szeredi Return-path: Received: from fg-out-1718.google.com ([72.14.220.158]:16286 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754247AbYAYNmR (ORCPT ); Fri, 25 Jan 2008 08:42:17 -0500 Received: by fg-out-1718.google.com with SMTP id e21so659897fga.17 for ; Fri, 25 Jan 2008 05:42:16 -0800 (PST) Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: [Miklos Szeredi - Fri, Jan 25, 2008 at 10:29:21AM +0100] | > | + /* is this correct? */ | > | + if (sbi->s_anchor[2] != 0) | > | + seq_printf(seq, ",anchor=%u", sbi->s_anchor[2]); | > | > you know, I would prefer to use form UDF_SB_ANCHOR(sb)[2] | > in sake of style unification but we should wait for Jan's | > decision (i'm not the expert in this area ;) | | I think UDF_SB_ANCHOR macro was removed by some patch in -mm. | | I'm more interested if the second element of the s_anchor array really | does always have the value of the 'anchor=N' mount option. I haven't | been able to verify that fully. Do you have some insight into that? | | Thanks, | Miklos | Hello Miklos, well, actually - no. anchor entities can be set to 0 if we have been failed to read them in udf_find_anchor(). So it seems you've to use some additional flag to store it. Btw, Miklos the patch is over -mm tree? - Cyrill -