On Mon 07-10-13 20:27:16, KOSAKI Motohiro wrote:
> (10/7/13 5:18 PM), Jan Kara wrote:
> >On Fri 04-10-13 16:42:19, KOSAKI Motohiro wrote:
> >>(10/4/13 4:31 PM), KOSAKI Motohiro wrote:
> >>>(10/2/13 4:29 PM), Jan Kara wrote:
> On Wed 02-10-13 09:20:09, Christoph Hellwig wrote:
> >On Wed, Oct
(10/7/13 5:18 PM), Jan Kara wrote:
On Fri 04-10-13 16:42:19, KOSAKI Motohiro wrote:
(10/4/13 4:31 PM), KOSAKI Motohiro wrote:
(10/2/13 4:29 PM), Jan Kara wrote:
On Wed 02-10-13 09:20:09, Christoph Hellwig wrote:
On Wed, Oct 02, 2013 at 04:27:41PM +0200, Jan Kara wrote:
Hello,
In my
On Fri 04-10-13 16:42:19, KOSAKI Motohiro wrote:
> (10/4/13 4:31 PM), KOSAKI Motohiro wrote:
> >(10/2/13 4:29 PM), Jan Kara wrote:
> >>On Wed 02-10-13 09:20:09, Christoph Hellwig wrote:
> >>>On Wed, Oct 02, 2013 at 04:27:41PM +0200, Jan Kara wrote:
> Hello,
>
> In my quest for
On Wed 02-10-13 09:20:09, Christoph Hellwig wrote:
> On Wed, Oct 02, 2013 at 04:27:41PM +0200, Jan Kara wrote:
> > Hello,
> >
> > In my quest for changing locking around page faults to make things easier
> > for
> > filesystems I found out get_user_pages() users could use a cleanup. The
> >
On Wed, Oct 02, 2013 at 04:27:41PM +0200, Jan Kara wrote:
> Hello,
>
> In my quest for changing locking around page faults to make things easier
> for
> filesystems I found out get_user_pages() users could use a cleanup. The
> knowledge about necessary locking for get_user_pages() is in tons
Hello,
In my quest for changing locking around page faults to make things easier for
filesystems I found out get_user_pages() users could use a cleanup. The
knowledge about necessary locking for get_user_pages() is in tons of places in
drivers and quite a few of them actually get it wrong (do
