linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: brauner@kernel.org, chuck.lever@oracle.com, bfields@fieldses.org,
	stable@vger.kernel.org, linux-nfs@vger.kernel.org, hch@lst.de,
	jlayton@kernel.org, vegard.nossum@oracle.com,
	naresh.kamboju@linaro.org
Subject: Re: [PATCH 6.1.y 0/2] Address ltp nfs test failure.
Date: Sun, 27 Aug 2023 09:57:34 +0200	[thread overview]
Message-ID: <2023082729-angles-aids-741f@gregkh> (raw)
In-Reply-To: <20230825161603.371792-1-harshit.m.mogalapalli@oracle.com>

On Fri, Aug 25, 2023 at 09:16:01AM -0700, Harshit Mogalapalli wrote:
> These two are backports for 6.1.y. Conflict resolution in done in
> both patches.
> 
> I have tested LTP-nfs fchown02 and chown02 on 6.1.y with below patches
> applied. The tests passed.
> 
> I would like to have a review as I am not familiar with this code.
> 
> Thanks to Vegard for helping me with this.
> 
> Thanks,
> Harshit
> 
> Christian Brauner (2):
>   nfs: use vfs setgid helper
>   nfsd: use vfs setgid helper
> 
>  fs/attr.c          | 1 +
>  fs/internal.h      | 2 --
>  fs/nfs/inode.c     | 4 +---
>  fs/nfsd/vfs.c      | 4 +++-
>  include/linux/fs.h | 2 ++
>  5 files changed, 7 insertions(+), 6 deletions(-)
> 
> -- 
> 2.34.1
> 

All now queued up, thanks.

greg k-h

      parent reply	other threads:[~2023-08-27  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 16:16 [PATCH 6.1.y 0/2] Address ltp nfs test failure Harshit Mogalapalli
2023-08-25 16:16 ` [PATCH 6.1.y 1/2] nfs: use vfs setgid helper Harshit Mogalapalli
2023-08-25 16:16 ` [PATCH 6.1.y 2/2] nfsd: " Harshit Mogalapalli
2023-08-25 23:11 ` [PATCH 6.1.y 0/2] Address ltp nfs test failure Daniel Díaz
2023-08-26 10:00   ` Harshit Mogalapalli
2023-08-27  7:57 ` Greg KH [this message]

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=2023082729-angles-aids-741f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bfields@fieldses.org \
    --cc=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=hch@lst.de \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=stable@vger.kernel.org \
    --cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).