Re: [efi:urgent 10/10] fs/efivarfs/super.c:424:27: error: use of undeclared identifier 'INODE_CHILD'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: kernel test robot <lkp@xxxxxxxxx>, Ard Biesheuvel <ardb@xxxxxxxxxx>
Subject: Re: [efi:urgent 10/10] fs/efivarfs/super.c:424:27: error: use of undeclared identifier 'INODE_CHILD'
From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 17 Mar 2025 08:33:16 -0400
Cc: llvm@xxxxxxxxxxxxxxx, oe-kbuild-all@xxxxxxxxxxxxxxx, linux-efi@xxxxxxxxxxxxxxx
In-reply-to: <202503171938.8Qee3VKa-lkp@intel.com>
References: <202503171938.8Qee3VKa-lkp@intel.com>
User-agent: Evolution 3.50.3

On Mon, 2025-03-17 at 19:49 +0800, kernel test robot wrote:
>  > 424		inode_lock_nested(inode, INODE_CHILD);

Sorry, was going to say on the other thread: the flag has to be
I_MUTEX_CHILD, Al just had a thinko when he wrote the above.

Regards,

James

Follow-Ups:
- Re: [efi:urgent 10/10] fs/efivarfs/super.c:424:27: error: use of undeclared identifier 'INODE_CHILD'
  - From: Ard Biesheuvel

References:
- [efi:urgent 10/10] fs/efivarfs/super.c:424:27: error: use of undeclared identifier 'INODE_CHILD'
  - From: kernel test robot

Prev by Date: [efi:urgent 10/10] fs/efivarfs/super.c:424:27: error: use of undeclared identifier 'INODE_CHILD'
Next by Date: Re: [PATCH 0/9] drivers: Transition to the faux device interface
Previous by thread: [efi:urgent 10/10] fs/efivarfs/super.c:424:27: error: use of undeclared identifier 'INODE_CHILD'
Next by thread: Re: [efi:urgent 10/10] fs/efivarfs/super.c:424:27: error: use of undeclared identifier 'INODE_CHILD'
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux