Re: [PATCH v2 1/3] f2fs: avoid opened loop codes in __add_ino_entry

On 2017/11/10 1:51, Jaegeuk Kim wrote: > Hi Chao, > > On 11/07, Chao Yu wrote: >> We will keep __add_ino_entry success all the time, for ENOMEM failure >> case, we have already handled it by using __GFP_NOFAIL flag, so we >> don't have to use additional opened loop codes here, remove them. >>

Re: [PATCH v2 1/3] f2fs: avoid opened loop codes in __add_ino_entry

On 2017/11/10 1:51, Jaegeuk Kim wrote: > Hi Chao, > > On 11/07, Chao Yu wrote: >> We will keep __add_ino_entry success all the time, for ENOMEM failure >> case, we have already handled it by using __GFP_NOFAIL flag, so we >> don't have to use additional opened loop codes here, remove them. >>

Re: [PATCH v2 1/3] f2fs: avoid opened loop codes in __add_ino_entry

Hi Chao, On 11/07, Chao Yu wrote: > We will keep __add_ino_entry success all the time, for ENOMEM failure > case, we have already handled it by using __GFP_NOFAIL flag, so we > don't have to use additional opened loop codes here, remove them. > > Signed-off-by: Chao Yu >

Re: [PATCH v2 1/3] f2fs: avoid opened loop codes in __add_ino_entry

Hi Chao, On 11/07, Chao Yu wrote: > We will keep __add_ino_entry success all the time, for ENOMEM failure > case, we have already handled it by using __GFP_NOFAIL flag, so we > don't have to use additional opened loop codes here, remove them. > > Signed-off-by: Chao Yu > --- > v2: > As Michal

[PATCH v2 1/3] f2fs: avoid opened loop codes in __add_ino_entry

We will keep __add_ino_entry success all the time, for ENOMEM failure case, we have already handled it by using __GFP_NOFAIL flag, so we don't have to use additional opened loop codes here, remove them. Signed-off-by: Chao Yu --- v2: As Michal Hocko suggested, with

[PATCH v2 1/3] f2fs: avoid opened loop codes in __add_ino_entry

We will keep __add_ino_entry success all the time, for ENOMEM failure case, we have already handled it by using __GFP_NOFAIL flag, so we don't have to use additional opened loop codes here, remove them. Signed-off-by: Chao Yu --- v2: As Michal Hocko suggested, with __GFP_NOFAIL, MM will do all