linux-kernel - Re: [RFC PATCH] nfs: Support posix_fadvise(POSIX_FADV

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: <20120623115106.GA2742@umich.edu>
Date:	Sat, 23 Jun 2012 07:51:06 -0400
From:	Jim Rees <rees@...ch.edu>
To:	Namjae Jeon <linkinjeon@...il.com>
Cc:	bfields@...ldses.org, Trond.Myklebust@...app.com,
	akpm@...ux-foundation.org, bharrosh@...asas.com,
	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	Namjae Jeon <namjae.jeon@...sung.com>,
	Vivek Trivedi <t.vivek@...sung.com>,
	Amit Sahrawat <a.sahrawat@...sung.com>
Subject: Re: [RFC PATCH] nfs: Support posix_fadvise(POSIX_FADV_RANDOM) on nfs
 server.

Namjae Jeon wrote:

  From: Namjae Jeon <namjae.jeon@...sung.com>
  
  This patch disable readahead for a file on NFS Server when
  posix_fadvise(fd..., POSIX_FADV_RANDOM) is called on NFS
  Client.

It looks like you're adding an argument to the read op.  Wouldn't that be an
incompatible change?  In which case wouldn't it be better to propose this
for inclusion in NFS 4.2?  In fact didn't Dean propose this?  What ever
happened with that?
--
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/