mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	NFS maillist <nfs@lists.sourceforge.net>
Subject: [PATCH] Fix NFS typos in 2.5.43...
Date: Wed, 16 Oct 2002 15:18:32 +0200	[thread overview]
Message-ID: <15789.26408.851059.191809@charged.uio.no> (raw)


The following patch fixes 2 obvious typos. Thanks to davem and George
Anzinger for pointing them out.

Cheers,
  Trond

diff -u --recursive --new-file linux-2.5.43/fs/nfs/inode.c linux-2.5.43-fixes/fs/nfs/inode.c
--- linux-2.5.43/fs/nfs/inode.c	2002-10-14 12:43:11.000000000 -0400
+++ linux-2.5.43-fixes/fs/nfs/inode.c	2002-10-16 08:44:04.000000000 -0400
@@ -1355,7 +1355,7 @@
 	if (data->auth_flavourlen != 0) {
 		if (data->auth_flavourlen > 1)
 			printk(KERN_INFO "NFS: cannot yet deal with multiple auth flavours.\n");
-		if (copy_from_user(authflavour, data->auth_flavours, sizeof(authflavour))) {
+		if (copy_from_user(&authflavour, data->auth_flavours, sizeof(authflavour))) {
 			err = -EFAULT;
 			goto out_fail;
 		}
diff -u --recursive --new-file linux-2.5.43/fs/nfs/proc.c linux-2.5.43-fixes/fs/nfs/proc.c
--- linux-2.5.43/fs/nfs/proc.c	2002-10-12 19:33:34.000000000 -0400
+++ linux-2.5.43-fixes/fs/nfs/proc.c	2002-10-16 08:44:29.000000000 -0400
@@ -490,7 +490,7 @@
 
 	dprintk("NFS call  fsinfo\n");
 	info->fattr->valid = 0;
-	status = rpc_call(server->client, NFSPROC_STATFS, fhandle, &info, 0);
+	status = rpc_call(server->client, NFSPROC_STATFS, fhandle, &fsinfo, 0);
 	dprintk("NFS reply fsinfo: %d\n", status);
 	if (status)
 		goto out;

                 reply	other threads:[~2002-10-16 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15789.26408.851059.191809@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®