From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= Subject: Partition device synchronisation Date: Fri, 11 May 2012 00:32:40 +0200 Message-ID: <4FAC4208.1070308@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig7EEFF62F55C838F206205A1C" To: linux-fsdevel@vger.kernel.org Return-path: Received: from mail-wg0-f44.google.com ([74.125.82.44]:60274 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932118Ab2EJWcx (ORCPT ); Thu, 10 May 2012 18:32:53 -0400 Received: by wgbdr13 with SMTP id dr13so1913614wgb.1 for ; Thu, 10 May 2012 15:32:52 -0700 (PDT) Sender: linux-fsdevel-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7EEFF62F55C838F206205A1C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, all. In GRUB we have tools to discover various parameters as to how GRUB would see the disks on boot and for this we run the same code as we have in boot time in userspace. So most natural for us would be accessing whole disks like sda but unfortunately its cache isn't kept synchronous with partitions (e.g. sda1), so if FS driver writes something to sda1 it won't be visible through sda until pages are dropped. Right now in Linux-specific code we try to find which partition of sda starts at given sector (e.g. 2048) by trying all partition Linux sees in order to read from sda1 rather than sda. The code is ugly and sometimes create issues. So my questions are: 1) Do we have to issue some ioctl to reload those caches? 2) Is it considered a bug and should I plunge forward, fix it and send a patch? --=20 Regards Vladimir '=CF=86-coder/phcoder' Serbinenko --------------enig7EEFF62F55C838F206205A1C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREKAAYFAk+sQgkACgkQNak7dOguQgkKgwEAv2qp/Ug7MeD6FsekcOvY7UYV 2qnvoVLjtk+SWU5acMkA/RS6G0LE2qNfP4KtBW0xn56E/sxb9OujvraWIU1i+dD2 =09Gp -----END PGP SIGNATURE----- --------------enig7EEFF62F55C838F206205A1C--