public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nscd/16878] New: nscd enters busy loop on long netgroup entry via nss_ldap of nslcd Date: Mon, 28 Apr 2014 16:22:00 -0000 [thread overview] Message-ID: <bug-16878-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16878 Bug ID: 16878 Summary: nscd enters busy loop on long netgroup entry via nss_ldap of nslcd Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: nscd Assignee: siddhesh at redhat dot com Reporter: siddhesh at redhat dot com CC: drepper.fsp at gmail dot com Description of problem: If there's a long (>1024 bytes) netgroup entry retrieved via nslcd's nss_ldap, nscd with netgroup caching enabled will enter a busy loop, hogging a CPU. Each repetition causes another nscd thread to busy loop, consequently using up all available CPU time. This is because nss_ldap (correctly) returns NSS_STATUS_TRYAGAIN if the provided buffer is not large enough to hold the result while nscd and the glibc nss modules for netgroups expect and set NSS_STATUS_UNAVAIL respectively. How reproducible: always Steps to Reproduce: 1. add long netgroup entry to LDAP 2. enable netgroup caching in nscd 3. getent netgroup longnetgroupentry Actual results: nscd thread enters busy loop, getent times out waiting for nscd and gets netgroup data directly Expected results: nscd returns netgroup data Patch coming up. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-04-28 16:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-28 16:22 siddhesh at redhat dot com [this message] 2014-04-30 9:10 ` [Bug nscd/16878] " siddhesh at redhat dot com 2014-05-26 6:10 ` cvs-commit at gcc dot gnu.org 2014-05-26 6:11 ` siddhesh at redhat dot com 2014-06-12 19:32 ` fweimer at redhat dot com 2014-06-12 19:33 ` fweimer at redhat dot com 2014-06-22 7:46 ` cvs-commit at gcc dot gnu.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-16878-131@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: linkBe 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).