mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "stable@kernel.org" <stable@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"trond.myklebust@hammerspace.com"
	<trond.myklebust@hammerspace.com>
Subject: Re: [PATCH 5.15 2/3] NFSv4: Clear NFS_CAP_OPEN_XOR and NFS_CAP_DELEGTIME if not supported
Date: Mon, 29 Sep 2025 14:04:26 +0000	[thread overview]
Message-ID: <f9a9080e416346d38d9a68ff560db4cd25601a56.camel@oracle.com> (raw)
In-Reply-To: <2025092903-plentiful-banister-9ad0@gregkh>

[-- Attachment #1: Type: text/plain, Size: 506 bytes --]

On Mon, Sep 29 2025 at 18:54:09 +0530, Greg Kroah-Hartman wrote:
> [...]
> >  			~(NFS_CAP_ACLS | NFS_CAP_HARDLINKS | NFS_CAP_SYMLINKS |
> > -			  NFS_CAP_SECURITY_LABEL | NFS_CAP_FS_LOCATIONS);
> > +			  NFS_CAP_SECURITY_LABEL | NFS_CAP_FS_LOCATIONS |
> > +			  NFS_CAP_OPEN_XOR | NFS_CAP_DELEGTIME);
> > [...]
> 
> This breaks the build :(

Oops, I am extremely sorry for posting this.

Please ignore/drop this one as those flags don't exist.

Build succeeds after this.

Thanks,
Siddh

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-09-29 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025091224-CVE-2025-39798-a66e@gregkh>
2025-09-25 12:58 ` [PATCH 5.15, 5.10, 5.4] NFSv4: Don't clear capabilities that won't be reset Siddh Raman Pant
2025-09-25 13:01   ` [PATCH 5.15 1/3] NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set Siddh Raman Pant
2025-09-25 13:01     ` [PATCH 5.15 2/3] NFSv4: Clear NFS_CAP_OPEN_XOR and NFS_CAP_DELEGTIME if not supported Siddh Raman Pant
2025-09-29 13:24       ` Greg Kroah-Hartman
2025-09-29 14:04         ` Siddh Raman Pant [this message]
2025-09-25 13:01     ` [PATCH 5.15 3/3] NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server Siddh Raman Pant
2025-09-25 13:02   ` [PATCH 5.10] " Siddh Raman Pant
2025-09-29 13:23   ` [PATCH 5.15, 5.10, 5.4] NFSv4: Don't clear capabilities that won't be reset Greg Kroah-Hartman

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=f9a9080e416346d38d9a68ff560db4cd25601a56.camel@oracle.com \
    --to=siddh.raman.pant@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=trond.myklebust@hammerspace.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®