This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
- From: Hal Murray <hmurray at megapathdsl dot net>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: libc-help at sourceware dot org, hmurray at megapathdsl dot net
- Date: Mon, 25 Sep 2017 10:23:52 -0700
- Subject: Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
- Authentication-results: sourceware.org; auth=none
carlos@redhat.com said:
> * Look to see if have a reasonable test that exercises this code path,
> and if not add one (I think there are tests already that cover this
> area of code).
Are there any tools that scan source code to check for this sort of thing?
I think you would need a way to annotate helper functions as needing a lock
and specify the lock. It may also take annotations in the caller function.
--
These are my opinions. I hate spam.