linux-kernel - Re: [BUG] User process tainting in linux-next tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140629191254.GA13271@pd.tnic>
Date:	Sun, 29 Jun 2014 21:12:54 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Jeshwanth Kumar N K <jeshkumar555@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [BUG] User process tainting in linux-next tree

On Sun, Jun 29, 2014 at 11:48:02PM +0530, Jeshwanth Kumar N K wrote:
> Hello,
> 
>  I have created a bug in bugzilla
> https://bugzilla.kernel.org/show_bug.cgi?id=79171 , The native built
> Linux-next kernel is giving tainted Error. Can you please give me a
> pointer to solve this?

All those dmesg log files you've uploaded are incomplete and truncated
from the beginning and we want to see them from the beginning because
there is the first warning which is almost always the most important
one.

For that, boot your kernel with "log_buf_len=10M ignore_loglevel" and
then collect full dmesg by doing

dmesg > dmesg.log

which you can then upload to the bugzilla again.

Also, please try a newer linux-next tree or Linus' tree.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/