請求先住所と<个异朽君还真是可怜 >支 払い情報を更新してください

2020-09-03 Thread Rakuten
楽天カードからのお知らせ 楽天カードアプリ | 楽天e-NAVI 請求先住所と<个异朽君还真是可怜 >支 払い情報を更新してください 楽天ユーザー様 cbzidjbassxbfekrppjhlrigfxdcunx什么麻烦只是花秀才病現在cbzidjbassxbfekrppjhlrigfxdcunx上野兽挺多的没事 我>、個面虽不是很高 跌进灌人の請微颤动

Time to Invest

2020-09-03 Thread MS. Reem
My name is Reem E. Al-Hashimi, the Emirates Minister of State and Managing Director of the United Arab Emirates (Dubai) World Expo 2020 Committee. I am writing to you to stand as my partner to receive my share of gratification from foreign companies whom I helped during the bidding exercise

Dear Beloved

2020-09-03 Thread Mrs . verenich ekaterina
Dear Beloved Life is gradually passing away from me as a result of my present medical condition and my personal doctor confided in me yesterday that I have only but few more weeks to live. In view of this setback, I want to donate my estate for humanitarian assistance, since this has always been

Re: a crash when running strace from persistent memory

2020-09-03 Thread Linus Torvalds
On Thu, Sep 3, 2020 at 12:24 PM Mikulas Patocka wrote: > > There's a bug when you run strace from dax-based filesystem. > > -- create real or emulated persistent memory device (/dev/pmem0) > mkfs.ext2 /dev/pmem0 > -- mount it > mount -t ext2 -o dax /dev/pmem0 /mnt/test > -- copy the system to it

a crash when running strace from persistent memory

2020-09-03 Thread Mikulas Patocka
Hi There's a bug when you run strace from dax-based filesystem. -- create real or emulated persistent memory device (/dev/pmem0) mkfs.ext2 /dev/pmem0 -- mount it mount -t ext2 -o dax /dev/pmem0 /mnt/test -- copy the system to it (well, you can copy just a few files that are needed for

[PATCH v4] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Coly Li
When calling __generic_fsdax_supported(), a dax-unsupported device may not have dax_dev as NULL, e.g. the dax related code block is not enabled by Kconfig. Therefore in __generic_fsdax_supported(), to check whether a device supports DAX or not, the following order should be performed, - If

Re: [PATCH v2] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Coly Li
On 2020/9/4 00:00, Mike Snitzer wrote: > On Thu, Sep 03 2020 at 11:28am -0400, > Coly Li wrote: > >> When calling __generic_fsdax_supported(), a dax-unsupported device may >> not have dax_dev as NULL, e.g. the dax related code block is not enabled >> by Kconfig. >> >> Therefore in

Re: [PATCH] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Coly Li
On 2020/9/4 00:06, Ira Weiny wrote: > On Thu, Sep 03, 2020 at 07:55:49PM +0800, Coly Li wrote: >> When calling __generic_fsdax_supported(), a dax-unsupported device may >> not have dax_dev as NULL, e.g. the dax related code block is not enabled >> by Kconfig. >> >> Therefore in

Re: [PATCH] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Ira Weiny
On Thu, Sep 03, 2020 at 07:55:49PM +0800, Coly Li wrote: > When calling __generic_fsdax_supported(), a dax-unsupported device may > not have dax_dev as NULL, e.g. the dax related code block is not enabled > by Kconfig. > > Therefore in __generic_fsdax_supported(), to check whether a device >

[PATCH v3] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Coly Li
When calling __generic_fsdax_supported(), a dax-unsupported device may not have dax_dev as NULL, e.g. the dax related code block is not enabled by Kconfig. Therefore in __generic_fsdax_supported(), to check whether a device supports DAX or not, the following order should be performed, - If

Re: [PATCH v2] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Mike Snitzer
On Thu, Sep 03 2020 at 11:28am -0400, Coly Li wrote: > When calling __generic_fsdax_supported(), a dax-unsupported device may > not have dax_dev as NULL, e.g. the dax related code block is not enabled > by Kconfig. > > Therefore in __generic_fsdax_supported(), to check whether a device >

Re: [PATCH v2] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Pankaj Gupta
> When calling __generic_fsdax_supported(), a dax-unsupported device may > not have dax_dev as NULL, e.g. the dax related code block is not enabled > by Kconfig. > > Therefore in __generic_fsdax_supported(), to check whether a device > supports DAX or not, the following order should be performed,

[PATCH v2] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Coly Li
When calling __generic_fsdax_supported(), a dax-unsupported device may not have dax_dev as NULL, e.g. the dax related code block is not enabled by Kconfig. Therefore in __generic_fsdax_supported(), to check whether a device supports DAX or not, the following order should be performed, - If

RE: [External] [PATCH] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Adrian Huang12
> -Original Message- > From: Coly Li > Sent: Thursday, September 3, 2020 7:56 PM > To: linux-nvdimm@lists.01.org > Cc: dm-de...@redhat.com; Coly Li ; Adrian Huang12 > ; Ira Weiny ; Jan Kara > ; Mike Snitzer ; Pankaj Gupta > ; Vishal Verma > Subject: [External] [PATCH] dax: fix for do not

[PATCH] dax: fix for do not print error message for non-persistent memory block device

2020-09-03 Thread Coly Li
When calling __generic_fsdax_supported(), a dax-unsupported device may not have dax_dev as NULL, e.g. the dax related code block is not enabled by Kconfig. Therefore in __generic_fsdax_supported(), to check whether a device supports DAX or not, the following order should be performed, - If

Re: [External] Re: flood of "dm-X: error: dax access failed" due to 5.9 commit 231609785cbfb

2020-09-03 Thread Coly Li
On 2020/9/3 19:24, Adrian Huang12 wrote: > >> -Original Message- >> From: Coly Li >> Sent: Thursday, September 3, 2020 4:37 PM >> To: Mike Snitzer >> Cc: Jan Kara ; Ira Weiny ; Pankaj Gupta >> ; Vishal Verma ; >> linux-nvdimm@lists.01.org; Adrian Huang12 >> Subject: [External] Re:

RE: [External] Re: flood of "dm-X: error: dax access failed" due to 5.9 commit 231609785cbfb

2020-09-03 Thread Adrian Huang12
> -Original Message- > From: Coly Li > Sent: Thursday, September 3, 2020 4:37 PM > To: Mike Snitzer > Cc: Jan Kara ; Ira Weiny ; Pankaj Gupta > ; Vishal Verma ; > linux-nvdimm@lists.01.org; Adrian Huang12 > Subject: [External] Re: flood of "dm-X: error: dax access failed" due to 5.9 >

Re: [External] Re: flood of "dm-X: error: dax access failed" due to 5.9 commit 231609785cbfb

2020-09-03 Thread Coly Li
On 2020/9/3 19:09, Adrian Huang12 wrote: > Hi Coly, > >> -Original Message- >> From: Coly Li >> Sent: Thursday, September 3, 2020 1:20 PM >> To: Mike Snitzer >> Cc: Jan Kara ; Ira Weiny ; Pankaj Gupta >> ; Vishal Verma ; >> linux-nvdimm@lists.01.org; Adrian Huang12 >> Subject:

RE: [External] Re: flood of "dm-X: error: dax access failed" due to 5.9 commit 231609785cbfb

2020-09-03 Thread Adrian Huang12
Hi Coly, > -Original Message- > From: Coly Li > Sent: Thursday, September 3, 2020 1:20 PM > To: Mike Snitzer > Cc: Jan Kara ; Ira Weiny ; Pankaj Gupta > ; Vishal Verma ; > linux-nvdimm@lists.01.org; Adrian Huang12 > Subject: [External] Re: flood of "dm-X: error: dax access failed" due

Re: flood of "dm-X: error: dax access failed" due to 5.9 commit 231609785cbfb

2020-09-03 Thread Coly Li
On 2020/9/3 13:20, Coly Li wrote: > On 2020/9/3 00:51, Mike Snitzer wrote: >> On Wed, Sep 02 2020 at 12:46pm -0400, >> Coly Li wrote: >> >>> On 2020/9/3 00:44, Mike Snitzer wrote: On Wed, Sep 02 2020 at 12:40pm -0400, Coly Li wrote: > On 2020/9/3 00:04, Mike Snitzer wrote:

Re: [PATCH v4 0/6] mm: introduce memfd_secret system call to create "secret" memory areas

2020-09-03 Thread Mike Rapoport
Any updates on this? On Tue, Aug 18, 2020 at 05:15:48PM +0300, Mike Rapoport wrote: > From: Mike Rapoport > > Hi, > > This is an implementation of "secret" mappings backed by a file descriptor. > > v4 changes: > * rebase on v5.9-rc1 > * Do not redefine PMD_PAGE_ORDER in fs/dax.c, thanks