On Mon, 2009-05-04 at 10:27 -0400, Chuck Lever wrote: > On May 2, 2009, at 4:12 AM, Peter Åstrand wrote: > > On Fri, 1 May 2009, Chuck Lever wrote: > > > >> The "intr" mount option has been deprecated for a while, but > >> /proc/mounts continues to display "nointr" whether "intr" or "nointr" > >> has been specified for a mount point. > >> > >> Since these options do not have any effect, simply do not display > >> them. > > > > Does this mean that "intr" is default now? Will the "intr" mount > > option > > still be accepted/ignored in the future? > > Since 2.6.25, the behavior of the NFS client has been a mix of the > two. I believe the current behavior is that SIGKILL can terminate an > NFS operation, but all other signals are deferred until pending NFS > operations complete. > > The mount command continues to accept both options, but neither have > any effect on the client's behavior (both options are no-ops). Note that this behaviour is true of local filesystems too, since generic_file_read() has been changed to call lock_page_killable() instead of the uninterruptible lock_page(). Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
