Bug 79171 - User process tainting in linux-next tree.
Summary: User process tainting in linux-next tree.
Status: NEW
Alias: None
Product: Other
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Bug Me Administrator
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-29 16:11 UTC by jeshkumar555@gmail.com
Modified: 2021-07-04 09:14 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.16.0-rc1-next-20140620+
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg log (125.90 KB, application/octet-stream)
2014-06-29 16:11 UTC, jeshkumar555@gmail.com 		Details
New dmesg (493.73 KB, application/octet-stream)
2014-06-29 18:10 UTC, jeshkumar555@gmail.com 		Details
New dmesg which starts from the beginning (92.78 KB, text/x-log)
2014-06-29 20:24 UTC, jeshkumar555@gmail.com 		Details
Show Obsolete (1) Add an attachment (proposed patch, testcase, etc.)

Description jeshkumar555@gmail.com 2014-06-29 16:11:54 UTC 
Created attachment 141351 [details]
dmesg log

Hello,

I built the linux-next kernel with localmodconfig. But it is getting tainting while booting. please find the dmesg log attached.
Comment 1 jeshkumar555@gmail.com 2014-06-29 18:10:04 UTC 
Created attachment 141401 [details]
New dmesg
Comment 2 jeshkumar555@gmail.com 2014-06-29 20:24:06 UTC 
Created attachment 141431 [details]
New dmesg which starts from the beginning
Comment 3 Alexey Dobriyan 2014-07-09 12:32:28 UTC 
Not tainted
Tainted: G        W

------------
kernel is tainted because WARNING occured
G stands for Good
W stands for Warning

so it's about
WARNING: CPU: 0 PID: 55 at kernel/res_counter.c:28 res_counter_uncharge_until+0x84/0x110()

the rest are symptoms
Comment 4 Drei Eck 2021-07-04 09:14:29 UTC 
You reported this at the place where bugs for the bug tracker itself should be reported.

I suggest moving this bug report to the correct place and closing it here.
Note You need to log in before you can comment on or make changes to this bug.