Jan Kara 44f06ba829 udf: Fix leak of UTF-16 surrogates into encoded strings
OSTA UDF specification does not mention whether the CS0 charset in case
of two bytes per character encoding should be treated in UTF-16 or
UCS-2. The sample code in the standard does not treat UTF-16 surrogates
in any special way but on systems such as Windows which work in UTF-16
internally, filenames would be treated as being in UTF-16 effectively.
In Linux it is more difficult to handle characters outside of Base
Multilingual plane (beyond 0xffff) as NLS framework works with 2-byte
characters only. Just make sure we don't leak UTF-16 surrogates into the
resulting string when loading names from the filesystem for now.

CC: stable@vger.kernel.org # >= v4.6
Reported-by: Mingye Wang <arthur200126@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
2018-04-18 16:34:55 +02:00
..
2018-04-07 09:08:24 -07:00
2018-04-04 13:03:38 -07:00
2018-04-07 09:08:24 -07:00
2018-04-07 09:08:24 -07:00
2018-03-14 13:31:23 +01:00
2018-03-27 13:18:09 -04:00
2018-04-07 09:08:24 -07:00
2018-04-03 16:27:08 -04:00
2018-02-06 18:32:45 -08:00
2018-03-07 11:47:15 +01:00
2018-03-27 13:18:09 -04:00
2018-03-15 10:06:06 -07:00
2018-02-07 14:25:22 -08:00
2018-02-06 18:32:45 -08:00
2018-03-29 15:08:21 -04:00
2017-12-07 14:23:30 -05:00
2018-03-28 01:39:02 -04:00
2018-01-29 07:27:24 -08:00
2018-02-06 10:41:33 -08:00
2018-04-06 15:01:25 -07:00
2018-02-15 15:34:42 -05:00
2018-04-04 12:44:02 -07:00