about summary refs log tree commit diff
path: root/elf/tst-audit11mod2.map
diff options
context:
space:
mode:
authorNikita Popov <npv1310@gmail.com>2021-11-02 13:21:42 +0500
committerFlorian Weimer <fweimer@redhat.com>2021-11-04 19:59:42 +0100
commitff012870b2c02a62598c04daa1e54632e020fd7d (patch)
treef389a262f3485c0d2d7387a58a9e8b7ad4414302 /elf/tst-audit11mod2.map
parent9fea0f1a2a6e4f7946505c358ab99ea3ab846274 (diff)
downloadglibc-ff012870b2c02a62598c04daa1e54632e020fd7d.tar.gz
glibc-ff012870b2c02a62598c04daa1e54632e020fd7d.tar.xz
glibc-ff012870b2c02a62598c04daa1e54632e020fd7d.zip
gconv: Do not emit spurious NUL character in ISO-2022-JP-3 (bug 28524)
Bugfix 27256 has introduced another issue:
In conversion from ISO-2022-JP-3 encoding, it is possible
to force iconv to emit extra NUL character on internal state reset.
To do this, it is sufficient to feed iconv with escape sequence
which switches active character set.
The simplified check 'data->__statep->__count != ASCII_set'
introduced by the aforementioned bugfix picks that case and
behaves as if '\0' character has been queued thus emitting it.

To eliminate this issue, these steps are taken:
* Restore original condition
'(data->__statep->__count & ~7) != ASCII_set'.
It is necessary since bits 0-2 may contain
number of buffered input characters.
* Check that queued character is not NUL.
Similar step is taken for main conversion loop.

Bundled test case follows following logic:
* Try to convert ISO-2022-JP-3 escape sequence
switching active character set
* Reset internal state by providing NULL as input buffer
* Ensure that nothing has been converted.

Signed-off-by: Nikita Popov <npv1310@gmail.com>
Diffstat (limited to 'elf/tst-audit11mod2.map')
0 files changed, 0 insertions, 0 deletions