linux-kernel - Re: [PATCH] FAT: optimize FSINFO writeback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <873a9hfdqz.fsf@devron.myhome.or.jp>
Date:	Wed, 01 Jul 2009 09:28:20 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	steve@...idescorp.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] FAT: optimize FSINFO writeback

"Steven J. Magnani" <steve@...idescorp.com> writes:

>> Well, now, we are using sb->s_dirty for fsinfo, so I'm wondering why
>> this happen frequently.
>
> My scenario was modifying a sector of an existing file and using
> fdatasync() to flush it. The FSINFO sector was being updated even though
> nothing about the FAT layout had changed.

I see. Probably, I'm missing something, or handling of sb->s_dirt may be
buggy, or something.

If it was fixed, is this patch still needed?  I guess this patch would
still be useful on some case though.  If you can explain, it would be
good.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/