606602 – Unable to build glibc, panic in __invalid_creds()

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 606602 - Unable to build glibc, panic in __invalid_creds()

Summary: Unable to build glibc, panic in __invalid_creds()

Keywords:
Status:	CLOSED DUPLICATE of bug 578268
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	kernel
Sub Component:
Version:	6.0
Hardware:	All
OS:	Linux
Priority:	low
Severity:	urgent
Target Milestone:	rc
Target Release:	---
Assignee:	Red Hat Kernel Manager
QA Contact:	Red Hat Kernel QE team
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2010-06-22 03:39 UTC by Dennis Gilmore
Modified:	2010-07-28 18:12 UTC (History)
CC List:	5 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2010-07-28 18:12:29 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
screenshot of the kernel panic (14.63 KB, image/png) 2010-06-22 03:39 UTC, Dennis Gilmore	no flags	Details
View All

Description Dennis Gilmore 2010-06-22 03:39:54 UTC

Created attachment 425815 [details]
screenshot of the kernel panic

Description of problem:
We have a pair or RHEL-6 beta1 boxes in the fedora buildsys. we noticed that if a glibc build hits the builder the builder completely locks up.  I grabbed a recent rhel6 snapshot and installed mock from epel and tried to reproduce the issue. I was able to 
the last messages in the build log was

make -s subdir=crypt -C crypt ..=../ tests
make[2]: Entering directory `/builddir/build/BUILD/glibc-2.12-39-g765ade4/crypt'
make[2]: Leaving directory `/builddir/build/BUILD/glibc-2.12-39-g765ade4/crypt'
make -s subdir=nptl -C nptl ..=../ tests
make[2]: Entering directory `/builddir/build/BUILD/glibc-2.12-39-g765ade4/nptl'


running the nptl test it seems is causing a kernel panic.


Version-Release number of selected component (if applicable):
kernel-2.6.32-30.el6.x86_64


How reproducible:
always

Steps to Reproduce:
1. mock build rawhides glibc on a rhel6 host
2.
3.
  
Actual results:
kernel panic

Expected results:
shiny new bits :)

Additional info:

Comment 2 RHEL Program Management 2010-06-22 04:03:21 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Dennis Gilmore 2010-06-22 20:37:58 UTC

 ------------[ cut here ]------------
kernel BUG at kernel/cred.c:843!
invalid opcode: 0000 [#1] SMP 
last sysfs file: /sys/devices/virtio-pci/virtio1/block/vda/dev
CPU 2 
Modules linked in: ip6t_REJECT(U) nf_conntrack_ipv6(U) ip6table_filter(U) ip6_tables(U) ipv6(U) dm_mirror(U) dm_region_hash(U) dm_log(U) i2c_piix4(U) i2c_core(U) virtio_net(U) virtio_balloon(U) sg(U) ext4(U) mbcache(U) jbd2(U) sr_mod(U) cdrom(U) ata_generic(U) pata_acpi(U) virtio_blk(U) virtio_pci(U) virtio_ring(U) virtio(U) ata_piix(U) dm_mod(U) [last unloaded: scsi_wait_scan]

Modules linked in: ip6t_REJECT(U) nf_conntrack_ipv6(U) ip6table_filter(U) ip6_tables(U) ipv6(U) dm_mirror(U) dm_region_hash(U) dm_log(U) i2c_piix4(U) i2c_core(U) virtio_net(U) virtio_balloon(U) sg(U) ext4(U) mbcache(U) jbd2(U) sr_mod(U) cdrom(U) ata_generic(U) pata_acpi(U) virtio_blk(U) virtio_pci(U) virtio_ring(U) virtio(U) ata_piix(U) dm_mod(U) [last unloaded: scsi_wait_scan]
Pid: 32258, comm: ld-linux-x86-64 Not tainted 2.6.32-30.el6.x86_64 #1 Bochs
RIP: 0010:[<ffffffff810964e3>]  [<ffffffff810964e3>] __invalid_creds+0x53/0x60
RSP: 0018:ffff880077571d80  EFLAGS: 00010282
RAX: 0000000000000022 RBX: ffff8800371d3e40 RCX: 00000000000006d8
RDX: 0000000000000000 RSI: 0000000000000046 RDI: 0000000000000246
RBP: ffff880077571da0 R08: 00000000ffffffff R09: 00000000fffffffc
R10: 0000000000000002 R11: 0000000000000000 R12: ffff8800371d3e40
R13: 00000000003d0f00 R14: 00007ffd526e4ff0 R15: 00007ffd526e59e0
FS:  00007ffd544e8710(0000) GS:ffff880001f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007ffd48df9ff8 CR3: 000000007bcf8000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000                                                                                                                                              
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400                                                                                                                                              
Process ld-linux-x86-64 (pid: 32258, threadinfo ffff880077570000, task ffff8800048e5480)                                                                                                                       
Stack:                                                                                                                                                                                                         
 83ca480d000000f0 ffffffff8166477b 00000000003f3549 ffff8800771d60c0                                                                                                                                           
<0> ffff880077571de0 ffffffff810978dc 0000000000000286 0000000000000001                                                                                                                                        
<0> 00000000003d0f00 ffff8800771d60c0 0000000000000000 00007ffd526e4ff0                                                                                                                                        
Call Trace:                                                                                                                                                                                                    
 [<ffffffff810978dc>] copy_creds+0x28c/0x300                                                                                                                                                                   
 [<ffffffff8106840b>] copy_process+0x30b/0x1370                                                                                                                                                                
 [<ffffffff8105ae87>] ? wake_up_new_task+0xb7/0x110                                                                                                                                                            
 [<ffffffff81069504>] do_fork+0x94/0x480                                                                                                                                                                       
 [<ffffffff810a423b>] ? sys_futex+0x7b/0x170                                                                                                                                                                   
 [<ffffffff810d2882>] ? audit_syscall_entry+0x252/0x280                                                                                                                                                        
 [<ffffffff81011588>] sys_clone+0x28/0x30                                                                                                                                                                      
 [<ffffffff81013493>] stub_clone+0x13/0x20                                                                                                                                                                     
 [<ffffffff81013172>] ? system_call_fastpath+0x16/0x1b
Code: e0 48 8b 75 e8 48 c7 c7 f6 4d 66 81 31 c0 e8 65 d2 43 00 48 c7 c6 09 4e 66 81 48 89 df 65 48 8b 14 25 00 cc 00 00 e8 9d fe ff ff <0f> 0b eb fe 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 48 83 ec 10 
RIP  [<ffffffff810964e3>] __invalid_creds+0x53/0x60
 RSP <ffff880077571d80>
---[ end trace e2c8ad5872f61a56 ]---
Kernel panic - not syncing: Fatal exception
Pid: 32258, comm: ld-linux-x86-64 Tainted: G      D    2.6.32-30.el6.x86_64 #1
Call Trace:
 [<ffffffff814d3671>] panic+0x78/0x137
 [<ffffffff814d771c>] oops_end+0xdc/0xf0
 [<ffffffff8101730b>] die+0x5b/0x90
 [<ffffffff814d6fd4>] do_trap+0xc4/0x160
 [<ffffffff81014ec5>] do_invalid_op+0x95/0xb0
 [<ffffffff810964e3>] ? __invalid_creds+0x53/0x60
 [<ffffffff8111ac66>] ? __alloc_pages_nodemask+0xf6/0x7e0
 [<ffffffff81013f5b>] invalid_op+0x1b/0x20
 [<ffffffff810964e3>] ? __invalid_creds+0x53/0x60
 [<ffffffff810978dc>] copy_creds+0x28c/0x300
 [<ffffffff8106840b>] copy_process+0x30b/0x1370
 [<ffffffff8105ae87>] ? wake_up_new_task+0xb7/0x110
 [<ffffffff81069504>] do_fork+0x94/0x480
 [<ffffffff810a423b>] ? sys_futex+0x7b/0x170
 [<ffffffff810d2882>] ? audit_syscall_entry+0x252/0x280
 [<ffffffff81011588>] sys_clone+0x28/0x30
 [<ffffffff81013493>] stub_clone+0x13/0x20
 [<ffffffff81013172>] ? system_call_fastpath+0x16/0x1b


full traceback captured over serial console building F-13's glibc in mock.

Comment 4 Eric Sandeen 2010-06-23 15:47:00 UTC

/*
 * report use of invalid credentials
 */
void __invalid_creds(const struct cred *cred, const char *file, unsigned line)
{
        printk(KERN_ERR "CRED: Invalid credentials\n");
        printk(KERN_ERR "CRED: At %s:%u\n", file, line);
        dump_invalid_creds(cred, "Specified", current);
        BUG();
}


I'm not that familiar w/ this code, but I guess the kernel should have given more information about what the creds were, prior to the BUG() ...

-Eric

Comment 5 Dennis Gilmore 2010-07-06 16:42:23 UTC

bug#607648 looks similar  but the test case there did not trigger a panic.

Comment 6 Eric Paris 2010-07-07 22:10:32 UTC

likely dup of 578268 fixed in kernel-2.6.32-42.el6

Comment 8 RHEL Program Management 2010-07-28 16:57:40 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 9 Eric Paris 2010-07-28 18:12:29 UTC


*** This bug has been marked as a duplicate of bug 578268 ***

Note You need to log in before you can comment on or make changes to this bug.