diff options
author | Jan Beulich <JBeulich@suse.com> | 2012-10-04 17:13:24 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-10-06 03:04:58 +0900 |
commit | da99075c1d368315e1508b6143226c0d27b621e0 (patch) | |
tree | 1ceefd8dc83bcc569640b519c00b0313be88bf1e /arch/arm/mm/flush.c | |
parent | 214f766ea0909e743122966c4617b3a112e405d7 (diff) | |
download | op-kernel-dev-da99075c1d368315e1508b6143226c0d27b621e0.zip op-kernel-dev-da99075c1d368315e1508b6143226c0d27b621e0.tar.gz |
lib/vsprintf.c: improve standard conformance of sscanf()
Xen's pciback points out a couple of deficiencies with vsscanf()'s
standard conformance:
- Trailing character matching cannot be checked by the caller: With a
format string of "(%x:%x.%x) %n" absence of the closing parenthesis
cannot be checked, as input of "(00:00.0)" doesn't cause the %n to be
evaluated (because of the code not skipping white space before the
trailing %n).
- The parameter corresponding to a trailing %n could get filled even if
there was a matching error: With a format string of "(%x:%x.%x)%n",
input of "(00:00.0]" would still fill the respective variable pointed to
(and hence again make the mismatch non-detectable by the caller).
This patch aims at fixing those, but leaves other non-conforming aspects
of it untouched, among them these possibly relevant ones:
- improper handling of the assignment suppression character '*' (blindly
discarding all succeeding non-white space from the format and input
strings),
- not honoring conversion specifiers for %n, - not recognizing the C99
conversion specifier 't' (recognized by vsprintf()).
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/arm/mm/flush.c')
0 files changed, 0 insertions, 0 deletions