linux-kernel - Re: [PATCH] misc: pass miscdevice through file's private

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] [day] [month] [year] [list]

Message-ID: <20150331131920.GA6373@kroah.com>
Date:	Tue, 31 Mar 2015 15:19:20 +0200
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Tom Van Braeckel <tomvanbraeckel@...il.com>
Cc:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	samu.p.onkalo@...ia.com
Subject: Re: [PATCH] misc: pass miscdevice through file's private_data

On Tue, Mar 31, 2015 at 03:08:38PM +0200, Tom Van Braeckel wrote:
> >> Wait, didn't this break FUSE?  Or was that some other variant of this
> >> patch?
> 
> The fix for FUSE is in 4.0-rc5 and linux-next. Btrfs was not affected,
> in the end. All kernel code has been checked for potential regressions.
> 
> So in my opinion, the time has come to apply this patch to char-misc so
> it can get some more testing in linux-next...

What is "this patch"?  I don't see it in the email :)

Please resend it, I don't have it in my patch queue anymore.

thanks,

greg k-h
--
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/