From: Christoph Hellwig <hch@lst.de>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: bfields@fieldses.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fs/locks: don't mess with the address limit in compat_fcntl64
Date: Tue, 16 May 2017 13:50:29 +0200 [thread overview]
Message-ID: <20170516115029.GA17669@lst.de> (raw)
In-Reply-To: <1494931570.2852.3.camel@poochiereds.net>
On Tue, May 16, 2017 at 06:46:10AM -0400, Jeff Layton wrote:
> Erm...build break above though -- flock is a pointer there, so those
> should be "flock->...". I'll just squash that fix into the patch unless
> you need to send a respin for other reasons.
Thanks. I did a last minute fixup to factor this into a helper and messed
up..
next prev parent reply other threads:[~2017-05-16 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 20:33 rewrite file locking compat syscalls Christoph Hellwig
2017-05-15 20:33 ` [PATCH 1/2] fs/locks: pass kernel struct flock to fcntl_getlk/setlk Christoph Hellwig
2017-05-15 20:33 ` [PATCH 2/2] fs/locks: don't mess with the address limit in compat_fcntl64 Christoph Hellwig
2017-05-16 10:46 ` Jeff Layton
2017-05-16 11:50 ` Christoph Hellwig [this message]
2017-05-16 10:08 ` rewrite file locking compat syscalls Jeff Layton
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=20170516115029.GA17669@lst.de \
--to=hch@lst.de \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
/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).