On Tue, Mar 8, 2011 at 2:52 PM, Alex Efros wrote: > On Tue, Mar 08, 2011 at 02:05:46PM -0500, Mike Frysinger wrote: >> if there's a bug in glibc, an actual bug in bugs.g.o needs to be >> opened with real details/patches. otherwise, nothing is going to >> change. > > Actually, from initial discussion I got impression this is *well* known > (at least to PaX/Hardened/Glibc developers) issue, so there unlikely any > needs in opening new bug. And I don't have patch for glibc. If anyone > think it have sense to report this to gentoo's bugzilla - I'll do it.
nothing in the e-mail you quoted said this was a kernel bug. it did however say "glibc bug" multiple times. -mike
