public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ryao at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/17478] Fix off-by-one error in pthread_setname_np()
Date: Thu, 16 Oct 2014 05:24:00 -0000 [thread overview]
Message-ID: <bug-17478-131-VTJWkNbBgm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17478-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17478
--- Comment #3 from Richard Yao <ryao at gentoo dot org> ---
A minor correction. I used `snprintf()` to do the copy, not `strncpy()`. I just
got back from LinuxCon Europe and I am semi-jet lagged. I just pushed my
patches so that you can see them:
https://github.com/ryao/zfs/compare/pthread_setname_np-for-glibc-upstream
https://github.com/ryao/zfs/commit/0e67649ebc56f40f5eebca1f86e18f2e750dc002
It literally works with that patch and hits an assertion failure without it
(the VERIFY). The assertion failure is interesting because it seems that I was
lucky enough (unlucky enough?) for the code to be passing "arc_adapt_thread" as
the thread name.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-10-16 5:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 21:37 [Bug nptl/17478] New: " ryao at gentoo dot org
2014-10-16 5:10 ` [Bug nptl/17478] " ryao at gentoo dot org
2014-10-16 5:24 ` ryao at gentoo dot org [this message]
2014-10-16 5:24 ` ryao at gentoo dot org
2014-10-16 5:26 ` ryao at gentoo dot org
2014-10-16 7:35 ` schwab@linux-m68k.org
2014-10-16 14:44 ` ryao at gentoo dot org
2014-10-16 14:51 ` ryao at gentoo dot org
2014-10-16 14:52 ` schwab@linux-m68k.org
2014-10-16 15:06 ` ryao at gentoo dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-17478-131-VTJWkNbBgm@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).