linux-nvdimm@lists.01.org 被黑了！ 立即更改密码！
by linux-nvdimm＠lists.01.org
我问候你！
我有个坏消息。
22/08/2018 - 在这一天，我攻击了您的操作系统并完全访问了您的帐户 linux-nvdimm(a)lists.01.org。
就是这样。
在您当天连接的路由器的软件中，存在一个漏洞。
我首先攻击了这个路由器并将恶意代码放在上面。
当您通过Internet输入时，我的木马安装在您设备的操作系统上。
之后，我完成了你的磁盘转储（我有你所有的地址簿，查看网站的历史记录，所有文件，电话号码和所有联系人的地址）。
一个月前，我想锁定你的设备并要求少量资金解锁。
但我查看了您经常访问的网站。 你最喜欢的资源令我震惊。
我说的是成人网站。
我想说 - 你是个大变态者。你有一个令人眼花缭乱的幻想！
在那之后，我想到了一个想法。
我制作了你喜欢的成人网站的截图（你知道我的意思，是吗？）。
之后，我在浏览本网站时拍摄了你和你的娱乐照片（我使用了你设备的相机）。
结果很棒！ 不要犹豫！
我深信您不想向您的亲戚，朋友或同事展示这些照片。
我认为320美元对于我的沉默是少量的。
此外，我花了很多时间在你身上！
我在比特币接受钱。
我的BTC钱包： 1P7bLeCJywaaDRQpT7iwb4qzUHa4CpRFyP
您不知道如何补充比特币钱包？
在任何搜索引擎中写“如何补充btc钱包”。
这很简单。
对于付款，你有两天多一点（恰好50小时）。
别担心，计时器将在您打开此信件时开始。是的，是的..它已经开始了！
付款后，我的病毒和你的妥协自动毁灭。
如果我没有收到您指定的金额，您的设备将被屏蔽，您的所有联系人都会收到您娱乐的照片。
要谨慎！
- 不要试图找到并摧毁我的病毒！ （您的所有数据都已上传到远程服务器）
- 不要试图联系我（这是不可能的，我通过您的帐户向您发送了此电子邮件）
- 各种安全服务对您没有帮助;格式化磁盘或销毁设备也无济于事，因为您的数据已经在远程服务器上。
附：我保证，付款后我不会打扰你，因为你不是我唯一的客户。
这是一个黑客的荣誉准则。
从现在开始，我建议你使用好的防病毒软件并定期更新（每天几次）！
不要生我的气，每个人都有自己的工作。
再见。
2 years, 1 month
[PATCH] acpi/nfit: Fix user-initiated ARS to be "ARS-long" rather than "ARS-short"
by Dan Williams
A "short" ARS (address range scrub) instructs the platform firmware to
return known errors. In contrast, a "long" ARS instructs platform
firmware to arrange every data address on the DIMM to be read / checked
for poisoned data.
The conversion of the flags in commit d3abaf43bab8 "acpi, nfit: Fix
Address Range Scrub completion tracking", changed the meaning of passing
'0' to acpi_nfit_ars_rescan(). Previously '0' meant "not short", now '0'
is ARS_REQ_SHORT. Pass ARS_REQ_LONG to restore the expected scrub-type
behavior of user-initiated ARS sessions.
Fixes: d3abaf43bab8 ("acpi, nfit: Fix Address Range Scrub completion tracking")
Reported-by: Jacek Zloch <jacek.zloch(a)intel.com>
Cc: Vishal Verma <vishal.l.verma(a)intel.com>
Signed-off-by: Dan Williams <dan.j.williams(a)intel.com>
---
drivers/acpi/nfit/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
index 14d9f5bea015..5912d30020c7 100644
--- a/drivers/acpi/nfit/core.c
+++ b/drivers/acpi/nfit/core.c
@@ -1308,7 +1308,7 @@ static ssize_t scrub_store(struct device *dev,
if (nd_desc) {
struct acpi_nfit_desc *acpi_desc = to_acpi_desc(nd_desc);
- rc = acpi_nfit_ars_rescan(acpi_desc, 0);
+ rc = acpi_nfit_ars_rescan(acpi_desc, ARS_REQ_LONG);
}
device_unlock(dev);
if (rc)
2 years, 1 month
[PATCH 0/2] kvm: Use huge pages for DAX-backed files
by Barret Rhoden
This patch series depends on dax pages not being PageReserved. Once
that is in place, these changes will let KVM use huge pages with
dax-backed files. Without the PageReserved change, KVM and DAX still
work with these patches, simply without huge pages - which is the
current situation.
RFC/discussion thread:
https://lore.kernel.org/lkml/20181029210716.212159-1-brho@google.com/
Barret Rhoden (2):
mm: make dev_pagemap_mapping_shift() externally visible
kvm: Use huge pages for DAX-backed files
arch/x86/kvm/mmu.c | 34 ++++++++++++++++++++++++++++++++--
include/linux/mm.h | 3 +++
mm/memory-failure.c | 38 +++-----------------------------------
mm/util.c | 34 ++++++++++++++++++++++++++++++++++
4 files changed, 72 insertions(+), 37 deletions(-)
--
2.19.1.930.g4563a0d9d0-goog
2 years, 1 month
[PATCH 0/9] Allow persistent memory to be used like normal RAM
by Dave Hansen
Persistent memory is cool. But, currently, you have to rewrite
your applications to use it. Wouldn't it be cool if you could
just have it show up in your system like normal RAM and get to
it like a slow blob of memory? Well... have I got the patch
series for you!
This series adds a new "driver" to which pmem devices can be
attached. Once attached, the memory "owned" by the device is
hot-added to the kernel and managed like any other memory. On
systems with an HMAT (a new ACPI table), each socket (roughly)
will have a separate NUMA node for its persistent memory so
this newly-added memory can be selected by its unique NUMA
node.
This is highly RFC, and I really want the feedback from the
nvdimm/pmem folks about whether this is a viable long-term
perversion of their code and device mode. It's insufficiently
documented and probably not bisectable either.
Todo:
1. The device re-binding hacks are ham-fisted at best. We
need a better way of doing this, especially so the kmem
driver does not get in the way of normal pmem devices.
2. When the device has no proper node, we default it to
NUMA node 0. Is that OK?
3. We muck with the 'struct resource' code quite a bit. It
definitely needs a once-over from folks more familiar
with it than I.
4. Is there a better way to do this than starting with a
copy of pmem.c?
Here's how I set up a system to test this thing:
1. Boot qemu with lots of memory: "-m 4096", for instance
2. Reserve 512MB of physical memory. Reserving a spot a 2GB
physical seems to work: memmap=512M!0x0000000080000000
This will end up looking like a pmem device at boot.
3. When booted, convert fsdax device to "device dax":
ndctl create-namespace -fe namespace0.0 -m dax
4. In the background, the kmem driver will probably bind to the
new device.
5. Now, online the new memory sections. Perhaps:
grep ^MemTotal /proc/meminfo
for f in `grep -vl online /sys/devices/system/memory/*/state`; do
echo $f: `cat $f`
echo online > $f
grep ^MemTotal /proc/meminfo
done
Cc: Dan Williams <dan.j.williams(a)intel.com>
Cc: Dave Jiang <dave.jiang(a)intel.com>
Cc: Ross Zwisler <zwisler(a)kernel.org>
Cc: Vishal Verma <vishal.l.verma(a)intel.com>
Cc: Tom Lendacky <thomas.lendacky(a)amd.com>
Cc: Andrew Morton <akpm(a)linux-foundation.org>
Cc: Michal Hocko <mhocko(a)suse.com>
Cc: linux-nvdimm(a)lists.01.org
Cc: linux-kernel(a)vger.kernel.org
Cc: linux-mm(a)kvack.org
Cc: Huang Ying <ying.huang(a)intel.com>
Cc: Fengguang Wu <fengguang.wu(a)intel.com>
2 years, 1 month
linux-nvdimm@lists.01.org 被黑了！ 立即更改密码！
by linux-nvdimm＠lists.01.org
我问候你！
我有个坏消息。
22/08/2018 - 在这一天，我攻击了您的操作系统并完全访问了您的帐户 linux-nvdimm(a)lists.01.org。
就是这样。
在您当天连接的路由器的软件中，存在一个漏洞。
我首先攻击了这个路由器并将恶意代码放在上面。
当您通过Internet输入时，我的木马安装在您设备的操作系统上。
之后，我完成了你的磁盘转储（我有你所有的地址簿，查看网站的历史记录，所有文件，电话号码和所有联系人的地址）。
一个月前，我想锁定你的设备并要求少量资金解锁。
但我查看了您经常访问的网站。 你最喜欢的资源令我震惊。
我说的是成人网站。
我想说 - 你是个大变态者。你有一个令人眼花缭乱的幻想！
在那之后，我想到了一个想法。
我制作了你喜欢的成人网站的截图（你知道我的意思，是吗？）。
之后，我在浏览本网站时拍摄了你和你的娱乐照片（我使用了你设备的相机）。
结果很棒！ 不要犹豫！
我深信您不想向您的亲戚，朋友或同事展示这些照片。
我认为333美元对于我的沉默是少量的。
此外，我花了很多时间在你身上！
我在比特币接受钱。
我的BTC钱包： 1P7bLeCJywaaDRQpT7iwb4qzUHa4CpRFyP
您不知道如何补充比特币钱包？
在任何搜索引擎中写“如何补充btc钱包”。
这很简单。
对于付款，你有两天多一点（恰好50小时）。
别担心，计时器将在您打开此信件时开始。是的，是的..它已经开始了！
付款后，我的病毒和你的妥协自动毁灭。
如果我没有收到您指定的金额，您的设备将被屏蔽，您的所有联系人都会收到您娱乐的照片。
要谨慎！
- 不要试图找到并摧毁我的病毒！ （您的所有数据都已上传到远程服务器）
- 不要试图联系我（这是不可能的，我通过您的帐户向您发送了此电子邮件）
- 各种安全服务对您没有帮助;格式化磁盘或销毁设备也无济于事，因为您的数据已经在远程服务器上。
附：我保证，付款后我不会打扰你，因为你不是我唯一的客户。
这是一个黑客的荣誉准则。
从现在开始，我建议你使用好的防病毒软件并定期更新（每天几次）！
不要生我的气，每个人都有自己的工作。
再见。
2 years, 1 month
[driver-core PATCH v7 0/9] Add NUMA aware async_schedule calls
by Alexander Duyck
This patch set provides functionality that will help to improve the
locality of the async_schedule calls used to provide deferred
initialization.
This patch set originally started out focused on just the one call to
async_schedule_domain in the nvdimm tree that was being used to defer the
device_add call however after doing some digging I realized the scope of
this was much broader than I had originally planned. As such I went
through and reworked the underlying infrastructure down to replacing the
queue_work call itself with a function of my own and opted to try and
provide a NUMA aware solution that would work for a broader audience.
In addition I have added several tweaks and/or clean-ups to the front of the
patch set. Patches 1 through 4 address a number of issues that actually were
causing the existing async_schedule calls to not show the performance that
they could due to either not scaling on a per device basis, or due to issues
that could result in a potential deadlock. For example, patch 4 addresses the
fact that we were calling async_schedule once per driver instead of once
per device, and as a result we would have still ended up with devices
being probed on a non-local node without addressing this first.
RFC->v1:
Dropped nvdimm patch to submit later.
It relies on code in libnvdimm development tree.
Simplified queue_work_near to just convert node into a CPU.
Split up drivers core and PM core patches.
v1->v2:
Renamed queue_work_near to queue_work_node
Added WARN_ON_ONCE if we use queue_work_node with per-cpu workqueue
v2->v3:
Added Acked-by for queue_work_node patch
Continued rename from _near to _node to be consistent with queue_work_node
Renamed async_schedule_near_domain to async_schedule_node_domain
Renamed async_schedule_near to async_schedule_node
Added kerneldoc for new async_schedule_XXX functions
Updated patch description for patch 4 to include data on potential gains
v3->v4
Added patch to consolidate use of need_parent_lock
Make asynchronous driver probing explicit about use of drvdata
v4->v5
Added patch to move async_synchronize_full to address deadlock
Added bit async_probe to act as mutex for probe/remove calls
Added back nvdimm patch as code it relies on is now in Linus's tree
Incorporated review comments on parent & device locking consolidation
Rebased on latest linux-next
v5->v6:
Drop the "This patch" or "This change" from start of patch descriptions.
Drop unnecessary parenthesis in first patch
Use same wording for "selecting a CPU" in comments added in first patch
Added kernel documentation for async_probe member of device
Fixed up comments for async_schedule calls in patch 2
Moved code related setting async driver out of device.h and into dd.c
Added Reviewed-by for several patches
v6->v7:
Fixed typo which had kernel doc refer to "lock" when I meant "unlock"
Dropped "bool X:1" to "u8 X:1" from patch description
Added async_driver to device_private structure to store driver
Dropped unecessary code shuffle from async_probe patch
Reordered patches to move fixes up to front
Added Reviewed-by for several patches
Updated cover page and patch descriptions throughout the set
---
Alexander Duyck (9):
driver core: Move async_synchronize_full call
driver core: Establish clear order of operations for deferred probe and remove
device core: Consolidate locking and unlocking of parent and device
driver core: Probe devices asynchronously instead of the driver
workqueue: Provide queue_work_node to queue work near a given NUMA node
async: Add support for queueing on specific NUMA node
driver core: Attach devices on CPU local to device node
PM core: Use new async_schedule_dev command
libnvdimm: Schedule device registration on node local to the device
drivers/base/base.h | 4 +
drivers/base/bus.c | 46 ++---------
drivers/base/dd.c | 182 +++++++++++++++++++++++++++++++++++++++------
drivers/base/power/main.c | 12 +--
drivers/nvdimm/bus.c | 11 ++-
include/linux/async.h | 82 ++++++++++++++++++++
include/linux/device.h | 3 +
include/linux/workqueue.h | 2
kernel/async.c | 53 +++++++------
kernel/workqueue.c | 84 +++++++++++++++++++++
10 files changed, 380 insertions(+), 99 deletions(-)
--
2 years, 1 month
Third party accessed to linux-nvdimm@lists.01.org.
by Account Security
Hello!
I'm is very good programmer, known in darkweb as geoff01.
I hacked this mailbox more than six months ago,
through it I infected your operating system with a virus (trojan) created by me and have been spying for you a very long time.
I understand it is hard to believe, but you can check it yourself.
I'm sent this e-mail from your account. Try it yourself.
Even if you changed the password after that - it does not matter, my virus intercepted all the caching data on your computer
and automatically saved access for me.
I have access to all your accounts, social networks, email, browsing history.
Accordingly, I have the data of all your contacts, files from your computer, photos and videos.
I was most struck by the intimate content sites that you occasionally visit.
You have a very wild imagination, I tell you!
During your pastime and entertainment there, I took screenshot through the camera of your device, synchronizing with what you are watching.
Oh my god! You are so funny and excited!
I think that you do not want all your contacts to get these files, right?
If you are of the same opinion, then I think that $249 is quite a fair price to destroy the dirt I created.
Send the above amount on my BTC wallet (bitcoin): 1JRCbCH9E3iLhSXPTqtkgfAsJNT2xD74C5
As soon as the above amount is received, I guarantee that the data will be deleted, I do not need it.
Otherwise, these files and history of visiting sites will get all your contacts from your device.
Also, I'll send to everyone your contact access to your email and access logs, I have carefully saved it!
Since reading this letter you have 48 hours!
After your reading this message, I'll receive an automatic notification that you have seen the letter.
I hope I taught you a good lesson.
Do not be so nonchalant, please visit only to proven resources, and don't enter your passwords anywhere!
Good luck!
2 years, 1 month
Third party accessed to linux-nvdimm@lists.01.org.
by Account Security
Hello!
I'm is very good programmer, known in darkweb as geri00.
I hacked this mailbox more than six months ago,
through it I infected your operating system with a virus (trojan) created by me and have been spying for you a very long time.
I understand it is hard to believe, but you can check it yourself.
I'm sent this e-mail from your account. Try it yourself.
Even if you changed the password after that - it does not matter, my virus intercepted all the caching data on your computer
and automatically saved access for me.
I have access to all your accounts, social networks, email, browsing history.
Accordingly, I have the data of all your contacts, files from your computer, photos and videos.
I was most struck by the intimate content sites that you occasionally visit.
You have a very wild imagination, I tell you!
During your pastime and entertainment there, I took screenshot through the camera of your device, synchronizing with what you are watching.
Oh my god! You are so funny and excited!
I think that you do not want all your contacts to get these files, right?
If you are of the same opinion, then I think that $234 is quite a fair price to destroy the dirt I created.
Send the above amount on my BTC wallet (bitcoin): 1JRCbCH9E3iLhSXPTqtkgfAsJNT2xD74C5
As soon as the above amount is received, I guarantee that the data will be deleted, I do not need it.
Otherwise, these files and history of visiting sites will get all your contacts from your device.
Also, I'll send to everyone your contact access to your email and access logs, I have carefully saved it!
Since reading this letter you have 48 hours!
After your reading this message, I'll receive an automatic notification that you have seen the letter.
I hope I taught you a good lesson.
Do not be so nonchalant, please visit only to proven resources, and don't enter your passwords anywhere!
Good luck!
2 years, 1 month
Third party accessed to linux-nvdimm@lists.01.org.
by Account Security
Hello!
I'm is very good programmer, known in darkweb as alvan85.
I hacked this mailbox more than six months ago,
through it I infected your operating system with a virus (trojan) created by me and have been spying for you a very long time.
I understand it is hard to believe, but you can check it yourself.
I'm sent this e-mail from your account. Try it yourself.
Even if you changed the password after that - it does not matter, my virus intercepted all the caching data on your computer
and automatically saved access for me.
I have access to all your accounts, social networks, email, browsing history.
Accordingly, I have the data of all your contacts, files from your computer, photos and videos.
I was most struck by the intimate content sites that you occasionally visit.
You have a very wild imagination, I tell you!
During your pastime and entertainment there, I took screenshot through the camera of your device, synchronizing with what you are watching.
Oh my god! You are so funny and excited!
I think that you do not want all your contacts to get these files, right?
If you are of the same opinion, then I think that $280 is quite a fair price to destroy the dirt I created.
Send the above amount on my BTC wallet (bitcoin): 1JRCbCH9E3iLhSXPTqtkgfAsJNT2xD74C5
As soon as the above amount is received, I guarantee that the data will be deleted, I do not need it.
Otherwise, these files and history of visiting sites will get all your contacts from your device.
Also, I'll send to everyone your contact access to your email and access logs, I have carefully saved it!
Since reading this letter you have 48 hours!
After your reading this message, I'll receive an automatic notification that you have seen the letter.
I hope I taught you a good lesson.
Do not be so nonchalant, please visit only to proven resources, and don't enter your passwords anywhere!
Good luck!
2 years, 1 month
