Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: chao@kernel.org (Chao Yu)
Subject: [PREVIEW] [PATCH chao/erofs-dev 1/3] staging: erofs: harden inode lookup for 32-bit platforms
Date: Mon, 1 Oct 2018 18:25:03 +0800	[thread overview]
Message-ID: <d5ea340f-47c2-79fd-b69a-b7809d3fab11@kernel.org> (raw)
In-Reply-To: <fdfb248d-59ef-10fd-7203-94ade0096e1f@aol.com>

Hi Xiang,

On 2018-10-1 10:08, Gao Xiang wrote:
> Hi Chao,
> 
> On 2018/10/1 8:37, Chao Yu wrote:
>> Hi Xiang,
>>
>> Sorry for late response to those patches.
> 
> That doesn't matter I know you are now busy with f2fs stuffs. ;)

Yeah, still struggling in fixing quota bugs, and try to write several test case
for xfstest suit.. :P

> 
> I have to deal with internal reported issues which could impact our products
> and do more cleanup apart from stability fixes.
> 
> It seems that Linux-4.20 will be out weeks later, and we also need
> to prepare more for it.
> 
> 
> And I tend to make progress in moving into fs tree before the next LTS version,
> we need to do more...

Sounds a lot of pending work there. :)

> 
> Source code of previewed mkfs will be released this month and it also seems much work to clean up it.

I hope Guifu can help to handle those work.

Thanks,

> 
>>
>> On 2018-10-1 0:22, Gao Xiang wrote:
>>> Hi Chao,
>>>
>>> Could you help merge these patches into erofs-dev (rebased on the latest erofs-master)?
>>> I need to fix several issues reported these days formally.
>>
>> No problem.
>>
>>>
>>> If you have time, could you also take some time review these patches?
>>
>> Okay, will review them soon. :)
> 
> Thanks Chao :)
> 
> Thanks,
> Gao Xiang
> 
>>
>> Thanks,
>>
>>>
>>> Thanks,
>>> Gao Xiang
>>>
>>> On 2018/9/21 11:43, Gao Xiang wrote:
>>>> This patch introduces inode hash function, test and set callbacks,
>>>> and iget5_locked to find the right inode for 32-bit platforms.
>>>>
>>>> Signed-off-by: Gao Xiang <gaoxiang25 at huawei.com>

  reply	other threads:[~2018-10-01 10:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21  3:43 [PREVIEW] [PATCH chao/erofs-dev 1/3] staging: erofs: harden inode lookup for 32-bit platforms Gao Xiang
2018-09-21  3:43 ` [PREVIEW] [PATCH chao/erofs-dev 2/3] staging: erofs: fix race when the managed cache is enabled Gao Xiang
2018-10-01  9:49   ` Chao Yu
2018-10-01 11:37     ` Gao Xiang
2018-10-22  9:36     ` [PATCH v2 " Gao Xiang
2018-10-22  9:51     ` [PATCH chao/erofs-dev] staging: erofs: add a full barrier in erofs_workgroup_unfreeze Gao Xiang
2018-09-21  3:43 ` [PREVIEW] [PATCH chao/erofs-dev 3/3] staging: erofs: managed pages could be locked at the time of decompression Gao Xiang
2018-10-01 10:03   ` Chao Yu
2018-09-30 16:22 ` [PREVIEW] [PATCH chao/erofs-dev 1/3] staging: erofs: harden inode lookup for 32-bit platforms Gao Xiang
2018-10-01  0:37   ` Chao Yu
2018-10-01  2:08     ` Gao Xiang
2018-10-01 10:25       ` Chao Yu [this message]
2018-10-01 11:25         ` Gao Xiang
2018-10-01  1:57 ` Chao Yu
2018-10-01  2:40   ` Gao Xiang
2018-10-01  3:04     ` Chao Yu
2018-10-01  4:26       ` Gao Xiang
2018-10-01  4:32         ` [PREVIEW][PATCH v2 chao/erofs-dev] " Gao Xiang
2018-10-01  5:24           ` Chao Yu

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=d5ea340f-47c2-79fd-b69a-b7809d3fab11@kernel.org \
    --to=chao@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