linux-kernel - Re: processes hung after sys_renameat, and 'missing' processes

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20120608150153.GE1711@redhat.com>
Date:	Fri, 8 Jun 2012 11:01:53 -0400
From:	Dave Jones <davej@...hat.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Miklos Szeredi <mszeredi@...e.cz>, Jan Kara <jack@...e.cz>
Subject: Re: processes hung after sys_renameat, and 'missing' processes

On Fri, Jun 08, 2012 at 04:51:05PM +0200, Peter Zijlstra wrote:
 
 > >  > Now also compile tested with CONFIG_LOCK_STAT...
 > > 
 > > Doesn't apply against Linus' current tree.
 > > 
 > > $ cat ../lock| patch -p1
 > > patching file include/linux/lockdep.h
 > > Hunk #1 FAILED at 211.
 > > Hunk #2 FAILED at 254.
 > > Hunk #3 FAILED at 363.
 > > Hunk #4 FAILED at 414.
 > > 4 out of 4 hunks FAILED -- saving rejects to file include/linux/lockdep.h.rej
 > > patching file include/trace/events/lock.h
 > > Hunk #1 FAILED at 61.
 > > Hunk #2 FAILED at 78.
 > > 2 out of 2 hunks FAILED -- saving rejects to file include/trace/events/lock.h.rej
 > > patching file kernel/lockdep.c
 > > Hunk #1 FAILED at 541.
 > > Hunk #2 succeeded at 556 with fuzz 2.
 > > Hunk #3 FAILED at 3093.
 > > patch: **** malformed patch at line 268: ck,
 > 
 > weird:

gaah, it's quoted-printable damaged. When I save that in mutt, I get a file that contains crap like

-       lock->cpu =3D cpu;
-       lock->ip =3D ip;


	Dave

--
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/