All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: "Zhujia (Euler)" <zhujia13@huawei.com>,
	jaegeuk@kernel.org, chao@kernel.org
Cc: jaizhu.zj@gmail.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: fix to update new block address correctly for OPU
Date: Mon, 26 Nov 2018 15:08:44 +0800	[thread overview]
Message-ID: <949f3ac3-c4d0-9a9a-8602-160794922cab@huawei.com> (raw)
In-Reply-To: <83d1b94c-9eb3-19a7-8340-ba111128f7ae@huawei.com>

Hi Jia,

On 2018/11/26 11:48, Zhujia (Euler) wrote:
> Hi  Chao,
> 
> On 2018/11/26 10:01, Chao Yu wrote:
>> On 2018/11/25 6:17, Jia Zhu wrote:
>>> Previously, we allocated a new block address for OPU mode in direct_IO.
>>>
>>> But the new address couldn't be assigned to @map->m_pblk correctly.
>>>
>>> This patch fix it.
>> Sorry to introduce this bug...
>>
>> It needs to Cc stable kernel mailing list and add 'Fixes' tag line.
> 
> I have checked the stable kernel branch and it hasn't merged the previous patch yet.
> 
> Shall we still need to cc stable kernel mailing list and add 'Fixes' tag line?

Yes, please.

I think it will be useful to track important fixes to troubleshoot user
reported bug in mailing list or bugzilla, in addition, I think it can be
the hint for maintainers of other distribution of linux e.g. redhat, suse..
to backport fixes to their own version of kernel.

Thanks,

> 
> Thanks,
> 
> Jia Zhu
> 
>>> Signed-off-by: Jia Zhu <zhujia13@huawei.com>
>> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>>
>> Thanks,
>>
>>> ---
>>>  fs/f2fs/data.c | 4 +++-
>>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>>> index 7226300..a3a567a 100644
>>> --- a/fs/f2fs/data.c
>>> +++ b/fs/f2fs/data.c
>>> @@ -1110,8 +1110,10 @@ int f2fs_map_blocks(struct inode *inode, struct f2fs_map_blocks *map,
>>>  		if (test_opt(sbi, LFS) && flag == F2FS_GET_BLOCK_DIO &&
>>>  							map->m_may_create) {
>>>  			err = __allocate_data_block(&dn, map->m_seg_type);
>>> -			if (!err)
>>> +			if (!err) {
>>> +				blkaddr = dn.data_blkaddr;
>>>  				set_inode_flag(inode, FI_APPEND_WRITE);
>>> +			}
>>>  		}
>>>  	} else {
>>>  		if (create) {
>>>
>>
>> .
>>
> 
> 
> .
> 

      reply	other threads:[~2018-11-26  7:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 22:17 [PATCH] f2fs: fix to update new block address correctly for OPU Jia Zhu
2018-11-26  2:01 ` Chao Yu
2018-11-26  3:48   ` Zhujia (Euler)
2018-11-26  7:08     ` Chao Yu [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=949f3ac3-c4d0-9a9a-8602-160794922cab@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=jaizhu.zj@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=zhujia13@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.