From: Souptick Joarder <jrdr.linux@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2] fs: fuse: Adding new return type vm_fault_t
Date: Tue, 26 Jun 2018 19:05:41 +0530 [thread overview]
Message-ID: <CAFqt6zZHY90RKYqtDUQ3gLu8t5mv0+Gi=Cd+cX=9GjPjqaDJog@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegvEKGdJe2+7rnz-xdkH5+xKN3wWnOEitx_9bz8spXgc0Q@mail.gmail.com>
On Tue, Jun 26, 2018 at 6:51 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Tue, Jun 26, 2018 at 9:52 AM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
>> On Sun, Jun 17, 2018 at 11:48 AM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
>>> On Wed, May 16, 2018 at 4:16 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
>>>> On Wed, May 16, 2018 at 6:45 AM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
>>>>> On Sat, May 12, 2018 at 10:25 AM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
>>>>>> Use new return type vm_fault_t for fault handler
>>>>>> in struct vm_operations_struct. For now, this is
>>>>>> just documenting that the function returns a
>>>>>> VM_FAULT value rather than an errno. Once all
>>>>>> instances are converted, vm_fault_t will become
>>>>>> a distinct type.
>>>>>>
>>>>>> commit 1c8f422059ae ("mm: change return type to
>>>>>> vm_fault_t")
>>>>>>
>>>>>> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
>>>>>> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
>>>>>> ---
>>>>>> fs/fuse/file.c | 2 +-
>>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
>>>>>> index a201fb0..67648cc 100644
>>>>>> --- a/fs/fuse/file.c
>>>>>> +++ b/fs/fuse/file.c
>>>>>> @@ -2048,7 +2048,7 @@ static void fuse_vma_close(struct vm_area_struct *vma)
>>>>>> * - sync(2)
>>>>>> * - try_to_free_pages() with order > PAGE_ALLOC_COSTLY_ORDER
>>>>>> */
>>>>>> -static int fuse_page_mkwrite(struct vm_fault *vmf)
>>>>>> +static vm_fault_t fuse_page_mkwrite(struct vm_fault *vmf)
>>>>>> {
>>>>>> struct page *page = vmf->page;
>>>>>> struct inode *inode = file_inode(vmf->vma->vm_file);
>>>>>> --
>>>>>> 1.9.1
>>>>>>
>>>>>
>>>>> Miklos, we would like to get this patch in queue
>>>>> for 4.18.
>>>>
>>>> Sure, queued up.
>>>>
>>>
>>> This patch is not merged in 4.18-rc-1
>>
>> Miklos, Can we get this patch in 4.18-rc-x / 4.19 ?
>
> Sure, queued up for 4.18-rc
> (git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#for-next).
>
> Sorry for the delay, somehow I left this off the 4.18 pull.
>
Thanks :)
prev parent reply other threads:[~2018-06-26 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 4:55 [PATCH v2] fs: fuse: Adding new return type vm_fault_t Souptick Joarder
2018-05-16 4:45 ` Souptick Joarder
2018-05-16 10:46 ` Miklos Szeredi
2018-06-17 6:18 ` Souptick Joarder
2018-06-26 7:52 ` Souptick Joarder
2018-06-26 13:21 ` Miklos Szeredi
2018-06-26 13:35 ` Souptick Joarder [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='CAFqt6zZHY90RKYqtDUQ3gLu8t5mv0+Gi=Cd+cX=9GjPjqaDJog@mail.gmail.com' \
--to=jrdr.linux@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=willy@infradead.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).