From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Eric Sandeen <sandeen@sandeen.net>
Subject: Re: [PATCH 2/2] xfs: compat_ioctl: use compat_ptr()
Date: Mon, 19 Aug 2019 09:42:18 -0700 [thread overview]
Message-ID: <20190819164218.GA1021238@magnolia> (raw)
In-Reply-To: <20190818083553.GA13583@infradead.org>
On Sun, Aug 18, 2019 at 01:35:53AM -0700, Christoph Hellwig wrote:
> On Fri, Aug 16, 2019 at 06:42:18PM -0700, Darrick J. Wong wrote:
> > On Fri, Aug 16, 2019 at 08:35:47AM +0200, Christoph Hellwig wrote:
> > > For 31-bit s390 user space, we have to pass pointer arguments through
> > > compat_ptr() in the compat_ioctl handler.
> > >
> > > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> >
> > Looks ok,
> > Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
>
> So, what is the plan? Do you think they are worth including for 5.3,
> or do you want to pass them off to Arnd for his series that is targeted
> at 5.4?
I'll combine these two with the reflink/dedupe locking fixes and push
all four out this week.
--D
prev parent reply other threads:[~2019-08-19 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 6:35 xfs compat ioctls fixlets Christoph Hellwig
2019-08-16 6:35 ` [PATCH 1/2] xfs: fall back to native ioctls for unhandled compat ones Christoph Hellwig
2019-08-16 13:51 ` Eric Sandeen
2019-08-17 1:42 ` Darrick J. Wong
2019-08-16 6:35 ` [PATCH 2/2] xfs: compat_ioctl: use compat_ptr() Christoph Hellwig
2019-08-16 14:05 ` Eric Sandeen
2019-08-17 1:42 ` Darrick J. Wong
2019-08-18 8:35 ` Christoph Hellwig
2019-08-19 16:42 ` Darrick J. Wong [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=20190819164218.GA1021238@magnolia \
--to=darrick.wong@oracle.com \
--cc=arnd@arndb.de \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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