2012-03-09 23:08:10 +00:00
|
|
|
{- GHC File system encoding handling.
|
2012-03-09 22:52:03 +00:00
|
|
|
-
|
2014-03-19 18:49:01 +00:00
|
|
|
- Copyright 2012-2014 Joey Hess <joey@kitenet.net>
|
2012-03-09 22:52:03 +00:00
|
|
|
-
|
2014-05-10 14:01:27 +00:00
|
|
|
- License: BSD-2-clause
|
2012-03-09 22:52:03 +00:00
|
|
|
-}
|
|
|
|
|
2014-03-19 18:49:01 +00:00
|
|
|
{-# LANGUAGE CPP #-}
|
|
|
|
|
2012-09-13 23:14:00 +00:00
|
|
|
module Utility.FileSystemEncoding (
|
|
|
|
fileEncoding,
|
|
|
|
withFilePath,
|
|
|
|
md5FilePath,
|
2014-03-19 18:49:01 +00:00
|
|
|
decodeBS,
|
2012-09-13 23:14:00 +00:00
|
|
|
decodeW8,
|
Fix a few bugs involving filenames that are at or near the filesystem's maximum filename length limit.
Started with a problem when running addurl on a really long url,
because the whole url is munged into the filename. Ended up doing
a fairly extensive review for places where filenames could get too large,
although it's hard to say I'm not missed any..
Backend.Url had a 128 character limit, which is fine when the limit is 255,
but not if it's a lot shorter on some systems. So check the pathconf()
limit. Note that this could result in fromUrl creating different keys
for the same url, if run on systems with different limits. I don't see
this is likely to cause any problems. That can already happen when using
addurl --fast, or if the content of an url changes.
Both Command.AddUrl and Backend.Url assumed that urls don't contain a
lot of multi-byte unicode, and would fail to truncate an url that did
properly.
A few places use a filename as the template to make a temp file.
While that's nice in that the temp file name can be easily related back to
the original filename, it could lead to `git annex add` failing to add a
filename that was at or close to the maximum length.
Note that in Command.Add.lockdown, the template is still derived from the
filename, just with enough space left to turn it into a temp file.
This is an important optimisation, because the assistant may lock down
a bunch of files all at once, and using the same template for all of them
would cause openTempFile to iterate through the same set of names,
looking for an unused temp file. I'm not very happy with the relatedTemplate
hack, but it avoids that slowdown.
Backend.WORM does not limit the filename stored in the key.
I have not tried to change that; so git annex add will fail on really long
filenames when using the WORM backend. It seems better to preserve the
invariant that a WORM key always contains the complete filename, since
the filename is the only unique material in the key, other than mtime and
size. Since nobody has complained about add failing (I think I saw it
once?) on WORM, probably it's ok, or nobody but me uses it.
There may be compatability problems if using git annex addurl --fast
or the WORM backend on a system with the 255 limit and then trying to use
that repo in a system with a smaller limit. I have not tried to deal with
those.
This commit was sponsored by Alexander Brem. Thanks!
2013-07-30 21:49:11 +00:00
|
|
|
encodeW8,
|
|
|
|
truncateFilePath,
|
2012-09-13 23:14:00 +00:00
|
|
|
) where
|
2012-03-09 22:52:03 +00:00
|
|
|
|
fix key directory hash calculation code
Fix Key directory hash calculation code to behave as it did before version
3.20120227 when a key contains non-ascii.
The hash directories for a given Key are based on its md5sum.
Prior to ghc 7.4, Keys contained raw, undecoded bytes, so the md5sum was
taken of each byte in turn. With the ghc 7.4 filename encoding change,
keys contains decoded unicode characters (possibly with surrigates for
undecodable bytes). This changes the result of the md5sum, since the md5sum
used is pure haskell and supports unicode. And that won't do, as git-annex
will start looking in a different hash directory for the content of a key.
The surrigates are particularly bad, since that's essentially a ghc
implementation detail, so could change again at any time. Also, changing
the locale changes how the bytes are decoded, which can also change
the md5sum.
Symptoms would include things like:
* git annex fsck would complain that no copies existed of a file,
despite its symlink pointing to the content that was locally present
* git annex fix would change the symlink to use the wrong hash
directory.
Only WORM backend is likely to have been affected, since only it tends
to include much filename data (SHA1E could in theory also be affected).
I have not tried to support the hash directories used by git-annex versions
3.20120227 to 3.20120308, so things added with those versions with WORM
will require manual fixups. Sorry for the inconvenience!
2012-03-09 23:26:02 +00:00
|
|
|
import qualified GHC.Foreign as GHC
|
|
|
|
import qualified GHC.IO.Encoding as Encoding
|
2012-03-09 23:08:10 +00:00
|
|
|
import Foreign.C
|
fix key directory hash calculation code
Fix Key directory hash calculation code to behave as it did before version
3.20120227 when a key contains non-ascii.
The hash directories for a given Key are based on its md5sum.
Prior to ghc 7.4, Keys contained raw, undecoded bytes, so the md5sum was
taken of each byte in turn. With the ghc 7.4 filename encoding change,
keys contains decoded unicode characters (possibly with surrigates for
undecodable bytes). This changes the result of the md5sum, since the md5sum
used is pure haskell and supports unicode. And that won't do, as git-annex
will start looking in a different hash directory for the content of a key.
The surrigates are particularly bad, since that's essentially a ghc
implementation detail, so could change again at any time. Also, changing
the locale changes how the bytes are decoded, which can also change
the md5sum.
Symptoms would include things like:
* git annex fsck would complain that no copies existed of a file,
despite its symlink pointing to the content that was locally present
* git annex fix would change the symlink to use the wrong hash
directory.
Only WORM backend is likely to have been affected, since only it tends
to include much filename data (SHA1E could in theory also be affected).
I have not tried to support the hash directories used by git-annex versions
3.20120227 to 3.20120308, so things added with those versions with WORM
will require manual fixups. Sorry for the inconvenience!
2012-03-09 23:26:02 +00:00
|
|
|
import System.IO
|
|
|
|
import System.IO.Unsafe
|
2012-03-10 15:38:38 +00:00
|
|
|
import qualified Data.Hash.MD5 as MD5
|
2012-06-20 16:51:25 +00:00
|
|
|
import Data.Word
|
|
|
|
import Data.Bits.Utils
|
2014-03-19 18:49:01 +00:00
|
|
|
import qualified Data.ByteString.Lazy as L
|
|
|
|
#ifdef mingw32_HOST_OS
|
|
|
|
import qualified Data.ByteString.Lazy.UTF8 as L8
|
|
|
|
#endif
|
2012-03-09 23:08:10 +00:00
|
|
|
|
|
|
|
{- Sets a Handle to use the filesystem encoding. This causes data
|
|
|
|
- written or read from it to be encoded/decoded the same
|
|
|
|
- as ghc 7.4 does to filenames etc. This special encoding
|
2014-03-19 18:49:01 +00:00
|
|
|
- allows "arbitrary undecodable bytes to be round-tripped through it".
|
|
|
|
-}
|
2012-03-09 23:08:10 +00:00
|
|
|
fileEncoding :: Handle -> IO ()
|
2014-03-19 18:49:01 +00:00
|
|
|
#ifndef mingw32_HOST_OS
|
fix key directory hash calculation code
Fix Key directory hash calculation code to behave as it did before version
3.20120227 when a key contains non-ascii.
The hash directories for a given Key are based on its md5sum.
Prior to ghc 7.4, Keys contained raw, undecoded bytes, so the md5sum was
taken of each byte in turn. With the ghc 7.4 filename encoding change,
keys contains decoded unicode characters (possibly with surrigates for
undecodable bytes). This changes the result of the md5sum, since the md5sum
used is pure haskell and supports unicode. And that won't do, as git-annex
will start looking in a different hash directory for the content of a key.
The surrigates are particularly bad, since that's essentially a ghc
implementation detail, so could change again at any time. Also, changing
the locale changes how the bytes are decoded, which can also change
the md5sum.
Symptoms would include things like:
* git annex fsck would complain that no copies existed of a file,
despite its symlink pointing to the content that was locally present
* git annex fix would change the symlink to use the wrong hash
directory.
Only WORM backend is likely to have been affected, since only it tends
to include much filename data (SHA1E could in theory also be affected).
I have not tried to support the hash directories used by git-annex versions
3.20120227 to 3.20120308, so things added with those versions with WORM
will require manual fixups. Sorry for the inconvenience!
2012-03-09 23:26:02 +00:00
|
|
|
fileEncoding h = hSetEncoding h =<< Encoding.getFileSystemEncoding
|
2014-03-19 18:49:01 +00:00
|
|
|
#else
|
|
|
|
{- The file system encoding does not work well on Windows,
|
|
|
|
- and Windows only has utf FilePaths anyway. -}
|
|
|
|
fileEncoding h = hSetEncoding h Encoding.utf8
|
|
|
|
#endif
|
2012-03-09 22:52:03 +00:00
|
|
|
|
|
|
|
{- Marshal a Haskell FilePath into a NUL terminated C string using temporary
|
|
|
|
- storage. The FilePath is encoded using the filesystem encoding,
|
|
|
|
- reversing the decoding that should have been done when the FilePath
|
|
|
|
- was obtained. -}
|
|
|
|
withFilePath :: FilePath -> (CString -> IO a) -> IO a
|
fix key directory hash calculation code
Fix Key directory hash calculation code to behave as it did before version
3.20120227 when a key contains non-ascii.
The hash directories for a given Key are based on its md5sum.
Prior to ghc 7.4, Keys contained raw, undecoded bytes, so the md5sum was
taken of each byte in turn. With the ghc 7.4 filename encoding change,
keys contains decoded unicode characters (possibly with surrigates for
undecodable bytes). This changes the result of the md5sum, since the md5sum
used is pure haskell and supports unicode. And that won't do, as git-annex
will start looking in a different hash directory for the content of a key.
The surrigates are particularly bad, since that's essentially a ghc
implementation detail, so could change again at any time. Also, changing
the locale changes how the bytes are decoded, which can also change
the md5sum.
Symptoms would include things like:
* git annex fsck would complain that no copies existed of a file,
despite its symlink pointing to the content that was locally present
* git annex fix would change the symlink to use the wrong hash
directory.
Only WORM backend is likely to have been affected, since only it tends
to include much filename data (SHA1E could in theory also be affected).
I have not tried to support the hash directories used by git-annex versions
3.20120227 to 3.20120308, so things added with those versions with WORM
will require manual fixups. Sorry for the inconvenience!
2012-03-09 23:26:02 +00:00
|
|
|
withFilePath fp f = Encoding.getFileSystemEncoding
|
|
|
|
>>= \enc -> GHC.withCString enc fp f
|
2012-03-09 23:08:10 +00:00
|
|
|
|
2012-09-13 23:14:00 +00:00
|
|
|
{- Encodes a FilePath into a String, applying the filesystem encoding.
|
|
|
|
-
|
|
|
|
- There are very few things it makes sense to do with such an encoded
|
|
|
|
- string. It's not a legal filename; it should not be displayed.
|
|
|
|
- So this function is not exported, but instead used by the few functions
|
|
|
|
- that can usefully consume it.
|
2012-03-09 23:08:10 +00:00
|
|
|
-
|
fix key directory hash calculation code
Fix Key directory hash calculation code to behave as it did before version
3.20120227 when a key contains non-ascii.
The hash directories for a given Key are based on its md5sum.
Prior to ghc 7.4, Keys contained raw, undecoded bytes, so the md5sum was
taken of each byte in turn. With the ghc 7.4 filename encoding change,
keys contains decoded unicode characters (possibly with surrigates for
undecodable bytes). This changes the result of the md5sum, since the md5sum
used is pure haskell and supports unicode. And that won't do, as git-annex
will start looking in a different hash directory for the content of a key.
The surrigates are particularly bad, since that's essentially a ghc
implementation detail, so could change again at any time. Also, changing
the locale changes how the bytes are decoded, which can also change
the md5sum.
Symptoms would include things like:
* git annex fsck would complain that no copies existed of a file,
despite its symlink pointing to the content that was locally present
* git annex fix would change the symlink to use the wrong hash
directory.
Only WORM backend is likely to have been affected, since only it tends
to include much filename data (SHA1E could in theory also be affected).
I have not tried to support the hash directories used by git-annex versions
3.20120227 to 3.20120308, so things added with those versions with WORM
will require manual fixups. Sorry for the inconvenience!
2012-03-09 23:26:02 +00:00
|
|
|
- This use of unsafePerformIO is belived to be safe; GHC's interface
|
|
|
|
- only allows doing this conversion with CStrings, and the CString buffer
|
|
|
|
- is allocated, used, and deallocated within the call, with no side
|
|
|
|
- effects.
|
|
|
|
-}
|
2012-09-13 23:14:00 +00:00
|
|
|
{-# NOINLINE _encodeFilePath #-}
|
|
|
|
_encodeFilePath :: FilePath -> String
|
|
|
|
_encodeFilePath fp = unsafePerformIO $ do
|
fix key directory hash calculation code
Fix Key directory hash calculation code to behave as it did before version
3.20120227 when a key contains non-ascii.
The hash directories for a given Key are based on its md5sum.
Prior to ghc 7.4, Keys contained raw, undecoded bytes, so the md5sum was
taken of each byte in turn. With the ghc 7.4 filename encoding change,
keys contains decoded unicode characters (possibly with surrigates for
undecodable bytes). This changes the result of the md5sum, since the md5sum
used is pure haskell and supports unicode. And that won't do, as git-annex
will start looking in a different hash directory for the content of a key.
The surrigates are particularly bad, since that's essentially a ghc
implementation detail, so could change again at any time. Also, changing
the locale changes how the bytes are decoded, which can also change
the md5sum.
Symptoms would include things like:
* git annex fsck would complain that no copies existed of a file,
despite its symlink pointing to the content that was locally present
* git annex fix would change the symlink to use the wrong hash
directory.
Only WORM backend is likely to have been affected, since only it tends
to include much filename data (SHA1E could in theory also be affected).
I have not tried to support the hash directories used by git-annex versions
3.20120227 to 3.20120308, so things added with those versions with WORM
will require manual fixups. Sorry for the inconvenience!
2012-03-09 23:26:02 +00:00
|
|
|
enc <- Encoding.getFileSystemEncoding
|
|
|
|
GHC.withCString enc fp $ GHC.peekCString Encoding.char8
|
2012-06-20 16:51:25 +00:00
|
|
|
|
2012-09-13 23:14:00 +00:00
|
|
|
{- Encodes a FilePath into a Md5.Str, applying the filesystem encoding. -}
|
|
|
|
md5FilePath :: FilePath -> MD5.Str
|
|
|
|
md5FilePath = MD5.Str . _encodeFilePath
|
|
|
|
|
2014-03-19 18:49:01 +00:00
|
|
|
{- Decodes a ByteString into a FilePath, applying the filesystem encoding. -}
|
|
|
|
decodeBS :: L.ByteString -> FilePath
|
|
|
|
#ifndef mingw32_HOST_OS
|
|
|
|
decodeBS = encodeW8 . L.unpack
|
|
|
|
#else
|
|
|
|
{- On Windows, we assume that the ByteString is utf-8, since Windows
|
|
|
|
- only uses unicode for filenames. -}
|
|
|
|
decodeBS = L8.toString
|
|
|
|
#endif
|
|
|
|
|
2012-06-20 16:51:25 +00:00
|
|
|
{- Converts a [Word8] to a FilePath, encoding using the filesystem encoding.
|
|
|
|
-
|
|
|
|
- w82c produces a String, which may contain Chars that are invalid
|
|
|
|
- unicode. From there, this is really a simple matter of applying the
|
|
|
|
- file system encoding, only complicated by GHC's interface to doing so.
|
|
|
|
-}
|
|
|
|
{-# NOINLINE encodeW8 #-}
|
|
|
|
encodeW8 :: [Word8] -> FilePath
|
|
|
|
encodeW8 w8 = unsafePerformIO $ do
|
|
|
|
enc <- Encoding.getFileSystemEncoding
|
|
|
|
GHC.withCString Encoding.char8 (w82s w8) $ GHC.peekCString enc
|
2012-09-13 23:14:00 +00:00
|
|
|
|
|
|
|
{- Useful when you want the actual number of bytes that will be used to
|
|
|
|
- represent the FilePath on disk. -}
|
|
|
|
decodeW8 :: FilePath -> [Word8]
|
|
|
|
decodeW8 = s2w8 . _encodeFilePath
|
Fix a few bugs involving filenames that are at or near the filesystem's maximum filename length limit.
Started with a problem when running addurl on a really long url,
because the whole url is munged into the filename. Ended up doing
a fairly extensive review for places where filenames could get too large,
although it's hard to say I'm not missed any..
Backend.Url had a 128 character limit, which is fine when the limit is 255,
but not if it's a lot shorter on some systems. So check the pathconf()
limit. Note that this could result in fromUrl creating different keys
for the same url, if run on systems with different limits. I don't see
this is likely to cause any problems. That can already happen when using
addurl --fast, or if the content of an url changes.
Both Command.AddUrl and Backend.Url assumed that urls don't contain a
lot of multi-byte unicode, and would fail to truncate an url that did
properly.
A few places use a filename as the template to make a temp file.
While that's nice in that the temp file name can be easily related back to
the original filename, it could lead to `git annex add` failing to add a
filename that was at or close to the maximum length.
Note that in Command.Add.lockdown, the template is still derived from the
filename, just with enough space left to turn it into a temp file.
This is an important optimisation, because the assistant may lock down
a bunch of files all at once, and using the same template for all of them
would cause openTempFile to iterate through the same set of names,
looking for an unused temp file. I'm not very happy with the relatedTemplate
hack, but it avoids that slowdown.
Backend.WORM does not limit the filename stored in the key.
I have not tried to change that; so git annex add will fail on really long
filenames when using the WORM backend. It seems better to preserve the
invariant that a WORM key always contains the complete filename, since
the filename is the only unique material in the key, other than mtime and
size. Since nobody has complained about add failing (I think I saw it
once?) on WORM, probably it's ok, or nobody but me uses it.
There may be compatability problems if using git annex addurl --fast
or the WORM backend on a system with the 255 limit and then trying to use
that repo in a system with a smaller limit. I have not tried to deal with
those.
This commit was sponsored by Alexander Brem. Thanks!
2013-07-30 21:49:11 +00:00
|
|
|
|
|
|
|
{- Truncates a FilePath to the given number of bytes (or less),
|
|
|
|
- as represented on disk.
|
|
|
|
-
|
|
|
|
- Avoids returning an invalid part of a unicode byte sequence, at the
|
|
|
|
- cost of efficiency when running on a large FilePath.
|
|
|
|
-}
|
|
|
|
truncateFilePath :: Int -> FilePath -> FilePath
|
2014-03-19 18:49:01 +00:00
|
|
|
#ifndef mingw32_HOST_OS
|
Fix a few bugs involving filenames that are at or near the filesystem's maximum filename length limit.
Started with a problem when running addurl on a really long url,
because the whole url is munged into the filename. Ended up doing
a fairly extensive review for places where filenames could get too large,
although it's hard to say I'm not missed any..
Backend.Url had a 128 character limit, which is fine when the limit is 255,
but not if it's a lot shorter on some systems. So check the pathconf()
limit. Note that this could result in fromUrl creating different keys
for the same url, if run on systems with different limits. I don't see
this is likely to cause any problems. That can already happen when using
addurl --fast, or if the content of an url changes.
Both Command.AddUrl and Backend.Url assumed that urls don't contain a
lot of multi-byte unicode, and would fail to truncate an url that did
properly.
A few places use a filename as the template to make a temp file.
While that's nice in that the temp file name can be easily related back to
the original filename, it could lead to `git annex add` failing to add a
filename that was at or close to the maximum length.
Note that in Command.Add.lockdown, the template is still derived from the
filename, just with enough space left to turn it into a temp file.
This is an important optimisation, because the assistant may lock down
a bunch of files all at once, and using the same template for all of them
would cause openTempFile to iterate through the same set of names,
looking for an unused temp file. I'm not very happy with the relatedTemplate
hack, but it avoids that slowdown.
Backend.WORM does not limit the filename stored in the key.
I have not tried to change that; so git annex add will fail on really long
filenames when using the WORM backend. It seems better to preserve the
invariant that a WORM key always contains the complete filename, since
the filename is the only unique material in the key, other than mtime and
size. Since nobody has complained about add failing (I think I saw it
once?) on WORM, probably it's ok, or nobody but me uses it.
There may be compatability problems if using git annex addurl --fast
or the WORM backend on a system with the 255 limit and then trying to use
that repo in a system with a smaller limit. I have not tried to deal with
those.
This commit was sponsored by Alexander Brem. Thanks!
2013-07-30 21:49:11 +00:00
|
|
|
truncateFilePath n = go . reverse
|
|
|
|
where
|
2014-10-09 18:53:13 +00:00
|
|
|
go f =
|
Fix a few bugs involving filenames that are at or near the filesystem's maximum filename length limit.
Started with a problem when running addurl on a really long url,
because the whole url is munged into the filename. Ended up doing
a fairly extensive review for places where filenames could get too large,
although it's hard to say I'm not missed any..
Backend.Url had a 128 character limit, which is fine when the limit is 255,
but not if it's a lot shorter on some systems. So check the pathconf()
limit. Note that this could result in fromUrl creating different keys
for the same url, if run on systems with different limits. I don't see
this is likely to cause any problems. That can already happen when using
addurl --fast, or if the content of an url changes.
Both Command.AddUrl and Backend.Url assumed that urls don't contain a
lot of multi-byte unicode, and would fail to truncate an url that did
properly.
A few places use a filename as the template to make a temp file.
While that's nice in that the temp file name can be easily related back to
the original filename, it could lead to `git annex add` failing to add a
filename that was at or close to the maximum length.
Note that in Command.Add.lockdown, the template is still derived from the
filename, just with enough space left to turn it into a temp file.
This is an important optimisation, because the assistant may lock down
a bunch of files all at once, and using the same template for all of them
would cause openTempFile to iterate through the same set of names,
looking for an unused temp file. I'm not very happy with the relatedTemplate
hack, but it avoids that slowdown.
Backend.WORM does not limit the filename stored in the key.
I have not tried to change that; so git annex add will fail on really long
filenames when using the WORM backend. It seems better to preserve the
invariant that a WORM key always contains the complete filename, since
the filename is the only unique material in the key, other than mtime and
size. Since nobody has complained about add failing (I think I saw it
once?) on WORM, probably it's ok, or nobody but me uses it.
There may be compatability problems if using git annex addurl --fast
or the WORM backend on a system with the 255 limit and then trying to use
that repo in a system with a smaller limit. I have not tried to deal with
those.
This commit was sponsored by Alexander Brem. Thanks!
2013-07-30 21:49:11 +00:00
|
|
|
let bytes = decodeW8 f
|
|
|
|
in if length bytes <= n
|
|
|
|
then reverse f
|
|
|
|
else go (drop 1 f)
|
2014-03-19 18:49:01 +00:00
|
|
|
#else
|
|
|
|
{- On Windows, count the number of bytes used by each utf8 character. -}
|
|
|
|
truncateFilePath n = reverse . go [] n . L8.fromString
|
|
|
|
where
|
|
|
|
go coll cnt bs
|
|
|
|
| cnt <= 0 = coll
|
|
|
|
| otherwise = case L8.decode bs of
|
|
|
|
Just (c, x) | c /= L8.replacement_char ->
|
|
|
|
let x' = fromIntegral x
|
|
|
|
in if cnt - x' < 0
|
|
|
|
then coll
|
|
|
|
else go (c:coll) (cnt - x') (L8.drop 1 bs)
|
|
|
|
_ -> coll
|
|
|
|
#endif
|