No luck ... ------------[ cut here ]------------ kernel BUG at fs/nfs/idmap.c:681! ACPI: Invalid Power Resource to register! invalid opcode: 0000 [#1] SMP Modules linked in: Pid: 145, comm: mount.nfs Not tainted 3.6.0-rc2 #22 System manufacturer System Product Name/K8N-DL EIP: 0060:[<c0596958>] EFLAGS: 00010286 CPU: 1 EIP is at nfs_idmap_legacy_upcall+0xf3/0x146 EAX: f5b5e1e0 EBX: f587e840 ECX: f5b5e000 EDX: 00000010 ESI: 00000010 EDI: f5b5e1f8 EBP: f5b77a6c ESP: f5b77a4c DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 CR0: 8005003b CR2: 0831e000 CR3: 35b5c000 CR4: 000007d0 DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 DR6: ffff0ff0 DR7: 00000400 Process mount.nfs (pid: 145, ti=f5b76000 task=f5b530c0 task.ti=f5b76000) Stack: f5b5e000 f5969a60 f5b5e1e0 f5b5e1a4 f5b5e1b4 c0596865 f59d0a00 f5969a60 f5b77aa0 c0600831 c09e626c c0a9d74c f5b5e180 f61dcd80 c0a9d758 f5970f80 f61dce00 00000000 00000003 f63d7f80 f5b5e194 f5b77ac0 c06008f0 00000000 Call Trace: [<c0596865>] ? idmap_pipe_destroy_msg+0x1d/0x1d [<c0600831>] request_key_and_link+0x297/0x30c [<c06008f0>] request_key_with_auxdata+0x19/0x44 [<c0596a44>] nfs_idmap_request_key+0x99/0x128 [<c0596bbd>] nfs_idmap_lookup_id+0x5a/0x95 [<c05972cc>] nfs_map_group_to_gid+0x3d/0x47 [<c05900b3>] decode_getfattr_attrs+0x539/0xa1b [<c05933ac>] decode_getfattr_generic.constprop.64+0x63/0x7f [<c05933d8>] decode_getfattr+0x10/0x12 [<c05935c0>] nfs4_xdr_dec_lookup_root+0x49/0x50 [<c0593577>] ? nfs4_xdr_dec_link+0x98/0x98 [<c07f765c>] rpcauth_unwrap_resp+0x48/0x50 [<c07f06af>] call_decode+0x260/0x2a3 [<c0593577>] ? nfs4_xdr_dec_link+0x98/0x98 [<c07f691e>] __rpc_execute+0x7c/0x1d9 [<c07f044f>] ? call_transmit_status+0x7c/0x7c [<c07f044f>] ? call_transmit_status+0x7c/0x7c [<c0440c35>] ? wake_up_bit+0x1c/0x20 [<c07f6b06>] rpc_execute+0x50/0x58 [<c07f1618>] rpc_run_task+0x67/0x6d [<c07f1706>] rpc_call_sync+0x40/0x5b [<c058a518>] _nfs4_call_sync+0x11/0x13 [<c058a3ac>] nfs4_call_sync+0x18/0x1d [<c058dafc>] nfs4_lookup_root+0x8d/0xb9 [<c058e75c>] nfs4_proc_get_rootfh+0x22/0x86 [<c05984d5>] nfs4_get_rootfh+0x31/0xa4 [<c04bff76>] ? kmem_cache_alloc_trace+0xc5/0xcf [<c057e624>] ? nfs_alloc_fattr+0x21/0x3a [<c07f6beb>] ? rpciod_up+0xf/0x18 [<c057e5e6>] ? nfs_fattr_init+0x21/0x3e [<c0598608>] nfs4_server_common_setup+0x45/0xab [<c0598b95>] nfs4_create_server+0x14b/0x171 [<c0595b9f>] nfs4_remote_mount+0x26/0x46 [<c04c7e55>] mount_fs+0x13/0x9a [<c04d8c51>] vfs_kern_mount+0x4f/0xa1 [<c0595a22>] nfs_do_root_mount+0x73/0x8d [<c0595bee>] nfs4_try_mount+0x2f/0x45 [<c058084b>] nfs_fs_mount+0x5cc/0x627 [<c0580c33>] ? nfs_clone_super+0x60/0x60 [<c057ea2c>] ? nfs_setattr+0x107/0x107 [<c04c7e55>] mount_fs+0x13/0x9a [<c04d8c51>] vfs_kern_mount+0x4f/0xa1 [<c04d8f63>] do_kern_mount+0x34/0xb2 [<c04da51b>] do_mount+0x5d8/0x626 [<c04da5cf>] sys_mount+0x66/0x99 [<c082209c>] sysenter_do_call+0x12/0x2c Code: 00 8d 93 84 00 00 00 8d 45 ec e8 42 d0 09 00 89 c6 8b 45 e8 85 f6 89 58 08 c7 40 0c 8c 00 00 00 78 2b 8b 4d e0 83 79 04 00 74 02 <0f> 0b 8b 45 e4 8b 4d e0 8b 55 e8 89 41 04 8b 01 e8 e8 94 26 00 EIP: [<c0596958>] nfs_idmap_legacy_upcall+0xf3/0x146 SS:ESP 0068:f5b77a4c ---[ end trace 9adee0a80860a05f ]--- -----Original Message----- From: Myklebust, Trond [mailto:Trond.Myklebust@xxxxxxxxxx] Sent: Thursday, August 16, 2012 5:22 PM To: Shai Lazmi Cc: William Dauchy; Schumaker, Bryan; linux-nfs@xxxxxxxxxxxxxxx Subject: Re: [PATCH 1/2] NFS: Clear key construction data if the idmap upcall fails On Thu, 2012-08-16 at 17:15 -0700, Shai Lazmi wrote: > git apply --check 0001-NFS-Clear-key-construction-data-if-the-idmap-upcall-.patch > error: patch failed: fs/nfs/idmap.c:61 > error: fs/nfs/idmap.c: patch does not apply > > > idmap.c > define NFS_UINT_MAXLEN 11 > > static const struct cred *id_resolver_cache; > static struct key_type key_type_id_resolver_legacy; > > struct idmap { > struct rpc_pipe *idmap_pipe; > struct key_construction *idmap_key_cons; > struct mutex idmap_mutex; > }; That's how it should more or less look after applying the patch. I'm guessing that one of your previous attempts has partially worked, and has left your checked out git tree in a "dirty" state. Please try the following: $ git reset --hard HEAD $ git apply --check 0001-NFS-Clear-key-construction-data-if-the-idmap-upcall-.patch $ git apply --check 0002-NFS-return-ENOKEY-when-the-upcall-fails-to-map-the-n.patch > > -----Original Message----- > From: Myklebust, Trond [mailto:Trond.Myklebust@xxxxxxxxxx] > Sent: Thursday, August 16, 2012 5:14 PM > To: Shai Lazmi > Cc: William Dauchy; Schumaker, Bryan; linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 1/2] NFS: Clear key construction data if the idmap upcall fails > > On Thu, 2012-08-16 at 17:07 -0700, Shai Lazmi wrote: > > Sorry - company's policy ... > > What idmap version was this patch used against? The one I have (b701358c) seems to be a bit different (I used latest pull commit ddf343f635fe4440cad528e12f96f28bd50aa099), hence the patch fails again > > It works fine for me against commit ddf343f635fe4440cad528e12f96f28bd50aa099: > > [trondmy@lade linux-nfs]$ git branch test-apply ddf343f635fe4440cad528e12f96f28bd50aa099 > [trondmy@lade linux-nfs]$ git checkout test-apply > Switched to branch 'test-apply' > [trondmy@lade linux-nfs]$ git am ~/Desktop/for_shai/0001-NFS-Clear-key-construction-data-if-the-idmap-upcall-.patch > Applying: NFS: Clear key construction data if the idmap upcall fails > [trondmy@lade linux-nfs]$ git am ~/Desktop/for_shai/0002-NFS-return-ENOKEY-when-the-upcall-fails-to-map-the-n.patch > Applying: NFS: return -ENOKEY when the upcall fails to map the name > > What error messages are you seeing? > > Cheers > Trond > > > -----Original Message----- > > From: Myklebust, Trond [mailto:Trond.Myklebust@xxxxxxxxxx] > > Sent: Thursday, August 16, 2012 4:57 PM > > To: Shai Lazmi > > Cc: William Dauchy; Schumaker, Bryan; linux-nfs@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH 1/2] NFS: Clear key construction data if the idmap upcall fails > > > > On Thu, 2012-08-16 at 16:50 -0700, Shai Lazmi wrote: > > > MS outlook > > > > Don't ever use LookOut for patches. Its "I just reformatted your email" > > wonder feature breaks all the whitespace. > > > > > Best thing is to attached the patch > > > > We do not normally use attachments on the mailing list because it makes it impossible to comment the patches inline. Ah well, here goes... > > > > -- > > Trond Myklebust > > Linux NFS client maintainer > > > > NetApp > > Trond.Myklebust@xxxxxxxxxx > > www.netapp.com > > > > > > This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. > > -- > Trond Myklebust > Linux NFS client maintainer > > NetApp > Trond.Myklebust@xxxxxxxxxx > www.netapp.com > > > This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. ��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
