linux-kernel - Re: [PATCH] usb: use memdup

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: <200905062044.38475.oliver@neukum.org>
Date:	Wed, 6 May 2009 20:44:38 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	david-b@...bell.net, lihong.hi@...il.com,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: use memdup_user()

Am Mittwoch, 6. Mai 2009 20:31:17 schrieb Andrew Morton:
> > > There must be some particular action which flips the thread of control
> > > from one state to the other.  eg, taking of a lock.
> >
> > Basically assigning an interface to the storage or ub driver.
>
> That's hardly enough information for anyone to understand what you
> mean :(

But isn't that always the same? If you take a lock that a method in the block
IO takes, you must use GFP_NOIO. What exactly do you want me to explain
better?

	Regards
		Oliver



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