Bug 696721

Summary: WARNING: at fs/hugetlbfs/inode.c:951 hugetlb_file_setup+0x227/0x250() triggered by trinity syscall fuzzer
Product: Red Hat Enterprise Linux 6 Reporter: Mike Gahagan <mgahagan>
Component: kernelAssignee: Larry Woodman <lwoodman>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: aarcange, aquini, jstancek
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-31 18:42:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 846704    
Attachments:
Description Flags
trinity run log none

Description Mike Gahagan 2011-04-14 17:56:32 UTC 
Description of problem:
Apr 14 11:00:55 test1239 kernel: ------------[ cut here ]------------
Apr 14 11:00:55 test1239 kernel: WARNING: at fs/hugetlbfs/inode.c:951 hugetlb_file_setup+0x227/0x250() (Not tainted)
Apr 14 11:00:55 test1239 kernel: Hardware name: KVM
Apr 14 11:00:55 test1239 kernel: Using mlock ulimits for SHM_HUGETLB deprecated
Apr 14 11:00:55 test1239 kernel: Modules linked in: tun fuse inet_diag hidp l2cap ipt_ULOG can af_802154 bluetooth rfkill pppoe pppo
x ppp_generic slhc atm rds af_key phonet autofs4 sunrpc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_RE
JECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 dm_mirror dm_region_hash dm_log microcod
e virtio_balloon snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc virtio_n
et i2c_piix4 i2c_core sg ext4 mbcache jbd2 virtio_blk sr_mod cdrom virtio_pci virtio_ring virtio ata_generic pata_acpi ata_piix dm_m
od [last unloaded: speedstep_lib]
Apr 14 11:00:55 test1239 kernel: Pid: 11828, comm: trinity Not tainted 2.6.32-131.0.1.el6.x86_64 #1
Apr 14 11:00:55 test1239 kernel: Call Trace:
Apr 14 11:00:55 test1239 kernel: [<ffffffff81067157>] ? warn_slowpath_common+0x87/0xc0
Apr 14 11:00:55 test1239 kernel: [<ffffffff81067246>] ? warn_slowpath_fmt+0x46/0x50
Apr 14 11:00:55 test1239 kernel: [<ffffffff81139a84>] ? user_shm_lock+0x54/0xc0
Apr 14 11:00:55 test1239 kernel: [<ffffffff811eac77>] ? hugetlb_file_setup+0x227/0x250
Apr 14 11:00:55 test1239 kernel: [<ffffffff8126ce60>] ? sprintf+0x40/0x50
Apr 14 11:00:55 test1239 kernel: [<ffffffff811f8612>] ? newseg+0x152/0x290
Apr 14 11:00:55 test1239 kernel: [<ffffffff811f39e5>] ? ipcget+0x1f5/0x200
Apr 14 11:00:55 test1239 kernel: [<ffffffff811f84a9>] ? sys_shmget+0x59/0x60
Apr 14 11:00:55 test1239 kernel: [<ffffffff811f84c0>] ? newseg+0x0/0x290
Apr 14 11:00:55 test1239 kernel: [<ffffffff811f84b0>] ? shm_security+0x0/0x10
Apr 14 11:00:55 test1239 kernel: [<ffffffff811f7c10>] ? shm_more_checks+0x0/0x20
Apr 14 11:00:55 test1239 kernel: [<ffffffff8100b172>] ? system_call_fastpath+0x16/0x1b
Apr 14 11:00:55 test1239 kernel: ---[ end trace 0546559542de2d10 ]---


Version-Release number of selected component (if applicable):
0413.0 tree, 131.0.1 kernel

How reproducible:
not certain, first time I"ve seen it.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 KernelOops Bot 2011-04-14 18:01:27 UTC 
 with this guiltyfunc:  bug 527824 bug 528295 bug 528296 bug 528521 bug 528768 bug 530380 bug 536855 bug 536985 bug 542694 bug 562008
Comment 3 Mike Gahagan 2011-04-14 18:01:54 UTC 
Created attachment 492183 [details]
trinity run log

Oops seems to happen just as the run started, 0xd0b77468 appears to the random seed value that was in use. See log for more info including syscalls made and their args.
Comment 4 Mike Gahagan 2011-04-14 18:08:14 UTC 
Another log with the same oops, on x86_64 bare metal system.

http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/04/726/72687/148840/1630226/6854590///test_log--kernel-syscalls-trinity.log
Comment 5 Larry Woodman 2011-08-05 12:22:01 UTC 
I havent seen this problem at all, can you see if its still reproducible in the latest RHEL6.2 kernel?

Larry Woodman
Comment 8 RHEL Program Management 2011-10-07 15:30:52 UTC 
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.