From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f65.google.com ([209.85.218.65]:37881 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388660AbeG1BXA (ORCPT ); Fri, 27 Jul 2018 21:23:00 -0400 Received: by mail-oi0-f65.google.com with SMTP id k81-v6so11972589oib.4 for ; Fri, 27 Jul 2018 16:58:47 -0700 (PDT) MIME-Version: 1.0 References: <153271267980.9458.7640156373438016898.stgit@warthog.procyon.org.uk> <153271291017.9458.7827028432894772673.stgit@warthog.procyon.org.uk> <21395.1532735340@warthog.procyon.org.uk> <21746.1532735504@warthog.procyon.org.uk> In-Reply-To: <21746.1532735504@warthog.procyon.org.uk> From: Jann Horn Date: Sat, 28 Jul 2018 01:58:19 +0200 Message-ID: Subject: Re: [PATCH 34/38] vfs: syscall: Add fsinfo() to query filesystem information [ver #10] To: David Howells Cc: Al Viro , Linux API , Linus Torvalds , linux-fsdevel@vger.kernel.org, kernel list Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Jul 28, 2018 at 1:51 AM David Howells wrote: > David Howells wrote: > > > One thing I'm confused about is that fat has both a codepage and a charset and > > I'm not sure of the difference. > > In fact, it's not clear that the codepage is actually used. > > warthog>git grep '[.>]codepage' > fs/fat/inode.c: opts->codepage = fat_default_codepage; > fs/fat/inode.c: opts->codepage = option; > fs/fat/inode.c: sprintf(buf, "cp%d", sbi->options.codepage); sprintf(buf, "cp%d", sbi->options.codepage); sbi->nls_disk = load_nls(buf); if (!sbi->nls_disk) { fat_msg(sb, KERN_ERR, "codepage %s not found", buf); goto out_fail; }