[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151005162802.GA11474@gmail.com>
Date: Mon, 5 Oct 2015 18:28:02 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@...il.com>,
Chris Metcalf <cmetcalf@...hip.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH] string: Improve the generic strlcpy() implementation
* Ingo Molnar <mingo@...nel.org> wrote:
> We could do something like:
>
> c = *(unsigned long *)(src+res);
> *(unsigned long *)(dest+res) = c;
>
> if (has_zero(c, &data, &constants)) {
> unsigned int zero_pos;
>
> data = prep_zero_mask(c, data, &constants);
> data = create_zero_mask(data);
>
> zero_pos = find_zero(data);
> res += zero_pos;
>
> memset(dest+res, 0, sizeof(long)-zero_pos);
>
> return res;
> }
>
> I.e. the extra memset() clears out the partial word (if any) after the NUL.
A slightly more paranoid version would be:
c = *(unsigned long *)(src+res);
if (has_zero(c, &data, &constants)) {
unsigned int zero_pos;
data = prep_zero_mask(c, data, &constants);
data = create_zero_mask(data);
zero_pos = find_zero(data);
/* Clear out undefined data within the final word after the NUL: */
memset((void *)&c + zero_pos, 0, sizeof(long)-zero_pos);
*(unsigned long *)(dest+res) = c;
return res+zero_pos;
}
*(unsigned long *)(dest+res) = c;
This would solve any theoretical races in the _target_ buffer: if the target
buffer may be copied to user-space in a racy fashion and we don't ever want it to
have undefined data, then this variant does the tail-zeroing of the final word in
the temporary copy, not in the target buffer.
Still untested.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists