On 08/19/13 10:51, Peng Haitao wrote: > The function lseek64() is thread safe. Applied. Thanks. Cheers, Michael > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/lseek64.3 | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/man3/lseek64.3 b/man3/lseek64.3 > index 8e5e88b..01e8e0d 100644 > --- a/man3/lseek64.3 > +++ b/man3/lseek64.3 > @@ -22,7 +22,7 @@ > .\" the source, must acknowledge the copyright and authors of this work. > .\" %%%LICENSE_END > .\" > -.TH LSEEK64 3 2004-12-11 "Linux" "Linux Programmer's Manual" > +.TH LSEEK64 3 2013-08-19 "Linux" "Linux Programmer's Manual" > .SH NAME > lseek64 \- reposition 64-bit read/write file offset > .SH SYNOPSIS > @@ -156,6 +156,11 @@ The prototype is: > .sp > For more details, see > .BR llseek (2). > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR lseek64 () > +function is thread-safe. > .SH SEE ALSO > .BR llseek (2), > .BR lseek (2) > -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
