[ndctl PATCH] Documentation/ndctl: fix a typo in ndctl(1)
by Vishal Verma
Fix 'namspaces' to 'namespaces' in the ndctl(1) man page.
Link: https://github.com/pmem/ndctl/issues/100
Reported-by: Steve Scargal <steve.scargall(a)intel.com>
Signed-off-by: Vishal Verma <vishal.l.verma(a)intel.com>
---
Documentation/ndctl/ndctl.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ndctl/ndctl.txt b/Documentation/ndctl/ndctl.txt
index b33e277..c2919de 100644
--- a/Documentation/ndctl/ndctl.txt
+++ b/Documentation/ndctl/ndctl.txt
@@ -30,7 +30,7 @@ message interface for platform NVDIMM resources like those defined by
the ACPI 6.0 NFIT (NVDIMM Firmware Interface Table). Operations
supported by the tool include, provisioning capacity (namespaces), as
well as enumerating/enabling/disabling the devices (dimms, regions,
-namspaces) associated with an NVDIMM bus.
+namespaces) associated with an NVDIMM bus.
include::../copyright.txt[]
--
2.20.1
2 years, 11 months
KZ Studio – Your Marketing Solution Partner
by KZ Studio – Your Marketing Solution Partner
Dear Valued Customer,
I am writing to introduce our company, KZ Studio Ltd.
KZ Studio provides One-stop services of project management (Included tech drawing, sourcing, production, logistics, installation & dismantle).
Our project included:
l Exhibition Booth
l Seasonal & Shopping Mall Decoration
l POP up store & Road show
l Window Display
l Shop Fitting & Retail Fixture
l POSM & Props
l Showcase Production & Rental
For more information, please visit our web site www.kz-studio.hk for more detail.
For enquiry, please reply this e-mail or contact our Account Manager, Mr. Him Ngan at (852) 2243 3303 or him.ngan(a)kz-studio.hk for further discussion.
BR,
Mr. Him Ngan
KZ Studio Ltd
Tel: (852) 2243 3303 | Mobile: (852) 9881 1650 | E-mail: him.ngan(a)kz-studio.hk
Website : www.kz-studio.hk
2 years, 11 months
专线物流助手
by Cain
你好！
我是做大陆到香港专线物流的Cain, 主要从事省内各地到香港葵涌码头、机场及其他站场的散货拼车，整车运输服务及香港到深圳的接驳运输，并可代理进出口报关报检配套服务
■ 大陆上门提货，运输报关一条龙服务
■ 香港有卸货平台，可提供装卸货，拼箱，仓储服务
■ 九龙/新界/港岛派送公司以及仓库
■ 香港机场/仓码头仓入仓服务
联系人:Cain QQ:737220804
Mobile：+86-15012841716(微信同号)
E-mail 1:xxyzeng@163.com
E-mail 2:Nol-hk-Cain@hotmail.com
香 港：葵涌三号货柜码头物流中心 A座地下
2 years, 11 months
Как продвигать свою компанию
by Stella Petrovna
Подробная информация>
Приглашаем Вас, в Одессу, Харьков или Днепр, на мастер-класс от Андрея Федорива "Папа бренда"
- Всем, кто хочет знать, как создать качественный бренд и превратить его в мощный инструмент;
- Возможно, это будет самый полезный мастер-класс в вашей жизни…
О чем мастер-класс?
Авторская методика «Папа бренда» от Андрея Федорива – ведущего маркетолога Восточной Европы и Центральной Азии с 20-летним опытом в развитии сотен успешных брендов в Украине, Казахстане, Азербайджане, России, а также в странах ЕС и Соединенных Штатах.
На примере практических кейсов, Папа Бренда покажет, как научиться создавать бренды на турбулентных рынках стран СНГ, брать бизнес в свои руки и добиваться грандиозных результатов. Мастер-класс о том, как превратить бренд в мощный инструмент изменений и роста.
Бизнес-программа:
1. Как жить? бренд как инструмент изменений
Жизнь, устав людей и что с этим делать. Новые герои и почему они ими стали
Знаю - Хочу - Плачу. Модель AIDA
2. Папа бренда
Типы владельцев бизнеса. Почему папа бренда?
Проходим тест на папу. А нужен ли маркетинг-директор? (нужен)
3. Отличайся
Стратегия = Идея. Как найти свою уникальную идею
4. Добротный кейс
Победы и провалы брендов Останкино, Папа может, Сосиска.ру
5. Потребитель
Ода исследованиям.
8 источников правдивой информации о потребителе.
Как искать инсайты. Кейсы хороших и плохих…
6. Стратегия
Цена - ценность. 5 уровней уникальности бренда.
Как сделать творческий прорыв.
Простые инструменты для придумывания.
7. Типичные стратегии
Можно выбрать типичную стратегию и наполнить её смыслом. Разберемся, как это сделать
8. Brand experience
Удовлетворение РАВНО результат МИНУС ожидание ПЕРЕВЫПОЛНЕНИЕ вместо ПЕРЕОБЕЩАНИЯ
Какой результат вы получите:
- Узнаете, как научиться создавать бренды на турбулентных рынках стран СНГ, брать бизнес в свои руки и добиваться грандиозных результатов.
- Научитесь создавать с нуля или возвращать к жизни плохо работающий бренд. На любом этапе бизнеса.
Подробная информация>
Отказ от почты. или пожаловаться на Спам!
List-Unsubscribe from the newsletter or complain about Spam!
2 years, 11 months
Re: Picking 0th namespace if it is idle
by Aneesh Kumar K.V
aneesh.kumar(a)linux.ibm.com (Aneesh Kumar K.V) writes:
> Hi Dan,
>
> With the patch series to mark the namespace disabled if we have mismatch
> in pfn superblock, we can endup with namespace0 marked idle/disabled.
>
> I am wondering why do do the below in ndctl.
>
>
> static struct ndctl_namespace *region_get_namespace(struct ndctl_region *region)
> {
> struct ndctl_namespace *ndns;
>
> /* prefer the 0th namespace if it is idle */
> ndctl_namespace_foreach(region, ndns)
> if (ndctl_namespace_get_id(ndns) == 0
> && !is_namespace_active(ndns))
> return ndns;
> return ndctl_region_get_namespace_seed(region);
> }
>
> I have a kernel patch that will create a namespace_seed even if we fail
> to ename a pfn backing device. Something like below
>
> @@ -747,12 +752,23 @@ static void nd_region_notify_driver_action(struct nvdimm_bus *nvdimm_bus,
> }
> }
> if (dev->parent && is_nd_region(dev->parent) && probe) {
> nd_region = to_nd_region(dev->parent);
> nvdimm_bus_lock(dev);
> if (nd_region->ns_seed == dev)
> nd_region_create_ns_seed(nd_region);
> nvdimm_bus_unlock(dev);
> }
> +
> + if (dev->parent && is_nd_region(dev->parent) && !probe && (ret == -EOPNOTSUPP)) {
> + nd_region = to_nd_region(dev->parent);
> + nvdimm_bus_lock(dev);
> + if (nd_region->ns_seed == dev)
> + nd_region_create_ns_seed(nd_region);
> + nvdimm_bus_unlock(dev);
> + }
> +
>
> With that we can end up with something like the below after boot.
> :/sys/bus/nd/devices/region0$ sudo ndctl list -Ni
> [
> {
> "dev":"namespace0.1",
> "mode":"fsdax",
> "map":"mem",
> "size":0,
> "uuid":"00000000-0000-0000-0000-000000000000",
> "state":"disabled"
> },
> {
> "dev":"namespace0.0",
> "mode":"fsdax",
> "map":"mem",
> "size":2147483648,
> "uuid":"094e703b-4bf8-4078-ad42-50bebc03e538",
> "state":"disabled"
> }
> ]
>
> namespace0.0 is the one we failed to initialize due to PAGE_SIZE
> mismatch.
>
> We do have namespace_seed pointing to namespacece0.1 correct. But a ndtl
> create-namespace will pick namespace0.0 even if we have seed file
> pointing to namespacec0.1.
>
>
> I am trying to resolve the issues related to creation of new namespaces
> when we have some namespace marked disabled due to pfn_sb setting
> mismatch.
>
> -aneesh
With that ndctl namespace0.0 selection commented out, we do get pick the
right idle namespace.
#ndctl list -Ni
[
{
"dev":"namespace0.1",
"mode":"fsdax",
"map":"mem",
"size":0,
"uuid":"00000000-0000-0000-0000-000000000000",
"state":"disabled"
},
{
"dev":"namespace0.0",
"mode":"fsdax",
"map":"mem",
"size":2147483648,
"uuid":"0c31ae4b-b053-43c7-82ff-88574e2585b0",
"state":"disabled"
}
]
after ndctl create-namespace -s 2G -r region0
# ndctl list -Ni
[
{
"dev":"namespace0.2",
"mode":"fsdax",
"map":"mem",
"size":0,
"uuid":"00000000-0000-0000-0000-000000000000",
"state":"disabled"
},
{
"dev":"namespace0.1",
"mode":"fsdax",
"map":"dev",
"size":2130706432,
"uuid":"60970059-9412-4eeb-9e7a-b314585a4da3",
"align":65536,
"blockdev":"pmem0.1",
"supported_alignments":[
65536
]
},
{
"dev":"namespace0.0",
"mode":"fsdax",
"map":"mem",
"size":2147483648,
"uuid":"0c31ae4b-b053-43c7-82ff-88574e2585b0",
"state":"disabled"
}
]
2 years, 11 months
Security Alert. Your accounts was compromised. You need change password!
by giles89
Hi, dear user of lists.01.org
We have installed one RAT software into you device
For this moment your email account is hacked too.
Changed your password? You're doing great!
But my software recognizes every such action. I'm updating passwords!
I'm always one step ahead....
So... I have downloaded all confidential information from your system and I got some more evidence.
The most interesting moment that I have discovered are videos records where you masturbating.
I posted EternalBlue Exploit modification on porn site, and then you installed my malicious code (trojan) on your operation system.
When you clicked the button Play on porn video, at that moment my trojan was downloaded to your device.
After installation, your front camera shoots video every time you masturbate, in addition, the software is synchronized with the video you choose.
For the moment, the software has harvrested all your contact information from social networks and email addresses.
If you need to erase all of your collected data and video with your enjoy, send me $600(usd) in BTC (crypto currency).
This is my Bitcoin wallet: 15Z4Y1q5QufvFPvRBKhwVhQyFTLwEQ5f4J
You have 48 hours after reading this letter.
After your transaction I will erase all your data.
Otherwise, I will send video with your pranks to all your colleagues, friends and relatives!!!
P.S. I'm asking you - not to answer this letter because the sender's address is fake, just to keep me incognito.
And henceforth be more careful!
Please visit only secure sites!
Bye,Bye...
2 years, 11 months
[PATCH v2 00/30] [RFC] virtio-fs: shared file system for virtual machines
by Vivek Goyal
Hi,
Here are the RFC patches for V2 of virtio-fs. These patches apply on top
of 5.1 kernel. These patches are also available here.
https://github.com/rhvgoyal/linux/commits/virtio-fs-dev-5.1
Patches for V1 were posted here.
https://lwn.net/ml/linux-fsdevel/20181210171318.16998-1-vgoyal@redhat.com/
This is still work in progress. As of now one can passthrough a host
directory in to guest and it works reasonably well. pjdfstests test
suite passes and blogbench runs. But this dirctory can't be shared
between guests and host can't modify files in directory yet. That's
still TBD.
Posting another version to gather feedback and comments on progress so far.
More information about the project can be found here.
https://virtio-fs.gitlab.io/
Changes from V1
===============
- Various bug fixes
- virtio-fs dax huge page size working, leading to improved performance.
- Fixed kernel automated tests warnings.
- Better handling of shared cache region reporting by virtio device.
Description from V1 posting
---------------------------
Problem Description
===================
We want to be able to take a directory tree on the host and share it with
guest[s]. Our goal is to be able to do it in a fast, consistent and secure
manner. Our primary use case is kata containers, but it should be usable in
other scenarios as well.
Containers may rely on local file system semantics for shared volumes,
read-write mounts that multiple containers access simultaneously. File
system changes must be visible to other containers with the same consistency
expected of a local file system, including mmap MAP_SHARED.
Existing Solutions
==================
We looked at existing solutions and virtio-9p already provides basic shared
file system functionality although does not offer local file system semantics,
causing some workloads and test suites to fail. In addition, virtio-9p
performance has been an issue for Kata Containers and we believe this cannot
be alleviated without major changes that do not fit into the 9P protocol.
Design Overview
===============
With the goal of designing something with better performance and local file
system semantics, a bunch of ideas were proposed.
- Use fuse protocol (instead of 9p) for communication between guest
and host. Guest kernel will be fuse client and a fuse server will
run on host to serve the requests. Benchmark results are encouraging and
show this approach performs well (2x to 8x improvement depending on test
being run).
- For data access inside guest, mmap portion of file in QEMU address
space and guest accesses this memory using dax. That way guest page
cache is bypassed and there is only one copy of data (on host). This
will also enable mmap(MAP_SHARED) between guests.
- For metadata coherency, there is a shared memory region which contains
version number associated with metadata and any guest changing metadata
updates version number and other guests refresh metadata on next
access. This is yet to be implemented.
How virtio-fs differs from existing approaches
==============================================
The unique idea behind virtio-fs is to take advantage of the co-location
of the virtual machine and hypervisor to avoid communication (vmexits).
DAX allows file contents to be accessed without communication with the
hypervisor. The shared memory region for metadata avoids communication in
the common case where metadata is unchanged.
By replacing expensive communication with cheaper shared memory accesses,
we expect to achieve better performance than approaches based on network
file system protocols. In addition, this also makes it easier to achieve
local file system semantics (coherency).
These techniques are not applicable to network file system protocols since
the communications channel is bypassed by taking advantage of shared memory
on a local machine. This is why we decided to build virtio-fs rather than
focus on 9P or NFS.
HOWTO
======
We have put instructions on how to use it here.
https://virtio-fs.gitlab.io/
Caching Modes
=============
Like virtio-9p, different caching modes are supported which determine the
coherency level as well. The “cache=FOO” and “writeback” options control the
level of coherence between the guest and host filesystems. The “shared” option
only has an effect on coherence between virtio-fs filesystem instances
running inside different guests.
- cache=none
metadata, data and pathname lookup are not cached in guest. They are always
fetched from host and any changes are immediately pushed to host.
- cache=always
metadata, data and pathname lookup are cached in guest and never expire.
- cache=auto
metadata and pathname lookup cache expires after a configured amount of time
(default is 1 second). Data is cached while the file is open (close to open
consistency).
- writeback/no_writeback
These options control the writeback strategy. If writeback is disabled,
then normal writes will immediately be synchronized with the host fs. If
writeback is enabled, then writes may be cached in the guest until the file
is closed or an fsync(2) performed. This option has no effect on mmap-ed
writes or writes going through the DAX mechanism.
- shared/no_shared
These options control the use of the shared version table. If shared mode
is enabled then metadata and pathname lookup is cached in guest, but is
refreshed due to changes in another virtio-fs instance.
DAX
===
- dax can be turned on/off when mounting virtio-fs inside guest.
TODO
====
- Implement "cache=shared" option.
- Improve error handling on host. If page fault on host fails, we need
to propagate it into guest.
- Try to fine tune for performance.
- Bug fixes
RESULTS
=======
- pjdfstests are passing. Have tried cache=none/auto/always and dax on/off).
https://github.com/pjd/pjdfstest
(one symlink test fails and that seems to be due xfs on host. Yet to
look into it).
- Ran blogbench and that works too.
Thanks
Vivek
Miklos Szeredi (2):
fuse: delete dentry if timeout is zero
fuse: Use default_file_splice_read for direct IO
Sebastien Boeuf (3):
virtio: Add get_shm_region method
virtio: Implement get_shm_region for PCI transport
virtio: Implement get_shm_region for MMIO transport
Stefan Hajnoczi (10):
fuse: export fuse_end_request()
fuse: export fuse_len_args()
fuse: export fuse_get_unique()
fuse: extract fuse_fill_super_common()
fuse: add fuse_iqueue_ops callbacks
virtio_fs: add skeleton virtio_fs.ko module
dax: remove block device dependencies
fuse, dax: add fuse_conn->dax_dev field
virtio_fs, dax: Set up virtio_fs dax_device
fuse, dax: add DAX mmap support
Vivek Goyal (15):
fuse: Clear setuid bit even in cache=never path
fuse: Export fuse_send_init_request()
fuse: Separate fuse device allocation and installation in fuse_conn
dax: Pass dax_dev to dax_writeback_mapping_range()
fuse: Keep a list of free dax memory ranges
fuse: Introduce setupmapping/removemapping commands
fuse, dax: Implement dax read/write operations
fuse: Define dax address space operations
fuse, dax: Take ->i_mmap_sem lock during dax page fault
fuse: Maintain a list of busy elements
fuse: Add logic to free up a memory range
fuse: Release file in process context
fuse: Reschedule dax free work if too many EAGAIN attempts
fuse: Take inode lock for dax inode truncation
virtio-fs: Do not provide abort interface in fusectl
drivers/dax/super.c | 3 +-
drivers/virtio/virtio_mmio.c | 32 +
drivers/virtio/virtio_pci_modern.c | 108 +++
fs/dax.c | 23 +-
fs/ext2/inode.c | 2 +-
fs/ext4/inode.c | 2 +-
fs/fuse/Kconfig | 11 +
fs/fuse/Makefile | 1 +
fs/fuse/control.c | 4 +-
fs/fuse/cuse.c | 5 +-
fs/fuse/dev.c | 80 +-
fs/fuse/dir.c | 28 +-
fs/fuse/file.c | 953 ++++++++++++++++++++++-
fs/fuse/fuse_i.h | 206 ++++-
fs/fuse/inode.c | 307 ++++++--
fs/fuse/virtio_fs.c | 1129 ++++++++++++++++++++++++++++
fs/splice.c | 3 +-
fs/xfs/xfs_aops.c | 2 +-
include/linux/dax.h | 6 +-
include/linux/fs.h | 2 +
include/linux/virtio_config.h | 17 +
include/uapi/linux/fuse.h | 34 +
include/uapi/linux/virtio_fs.h | 44 ++
include/uapi/linux/virtio_ids.h | 1 +
include/uapi/linux/virtio_mmio.h | 11 +
include/uapi/linux/virtio_pci.h | 10 +
26 files changed, 2875 insertions(+), 149 deletions(-)
create mode 100644 fs/fuse/virtio_fs.c
create mode 100644 include/uapi/linux/virtio_fs.h
--
2.20.1
2 years, 11 months
Практическое задание.
by Alexander
Содержание:
1. Управление рабочим временем в корпоративных продажах:
- Эффективное управление и планирование рабочего времени менеджера по продажам.
- Повышение личной продуктивности и эффективности.
- Поглотители рабочего времени.
- Хаос и порядок.
- Упражнение "Расчищение ментального пространства".
- Рабочие ключевые области.
- Принципы управления личной эффективностью и формирования рабочего плана распределения времени. Практическое задание.
- Философия и физиология эффективного тайм-менеджмента.
- Техника постановки достижимых целей.
- Упражнение "Целеполагание".
- Планирование и анализ рабочего времени: год-месяц-неделя-день.
2. Корпоративные стандарты продаж. эффективная работа с клиентской базой:
- Управление циклом продаж
- Корпоративный стандарт процесса продажи. Анализ процесса общения с клиентами.
- Шаги продажи.
- Сегментация клиентов.
- Обеспечение объемов продаж.
- Воронка продаж.
- Принцип "красных мундиров".
- Стратегии удержания клиентов и повышения их ценности для компании.
3. Эффективные коммуникации с клиентами - установление контакта. привлечение и удержание клиента:
- Правила эффективного взаимодействия с клиентами
- Типология психологических типов клиентов и принципы работы с каждым из них.
- Побудительные мотивы и работа с клиентом в зависимости от его побудительных мотивов.
- Упражнение "Побудительные мотивы".
- Ассертивные коммуникации.
- Виды влияния в коммуникациях:
- факты и искажения
- способы манипуляции в переговорах и общении с клиентами
- 16 законов убеждения
- треугольник АРО - вовлечение в продажу
- Шкала эмоций. Упражнение "Определение эмоционального тона".
- Техники подстройки.
- 8 пар Мета-программ человека. "Управляющие программы человека" - системы взглядов, которыми руководствуется человек принимая решение и осуществляя любую деятельность, классификация ключевых привычек мышления.
4. Работа с возражениями и выход из "тупика" в переговорах:
- Работа с возражениями и рекламациями.
- Принципы бесконфликтного общения.
- Упражнение "Нивелирование возражений":
- Правила диалога.
- Проведение переговоров.
- Видеосъемка с последующим анализом.
5. Личный план развития навыков.
- Горизонты жизни.
Методика обучения
- Мини-лекции
- Мозговой штурм
- Ролевые игры, индивидуальная и командная работа
- Тестирование
- Формирование программы развития.
Перейти на сайт>
Не получать рассылки. List-Unsubscribe или пожаловаться на Spam
2 years, 11 months
[PATCH v2 0/7] libnvdimm: Fix async operations and locking
by Dan Williams
Changes since v1 [1]:
- Fix an ioctl command corruption regression that manifested as an
intermittent failure of the monitor.sh unit test. This is handled in
the patch4 prep patch that makes it safe for nd_ioctl() to be
re-entrant. (Vishal)
- Update the changelog for the driver-core 'lockdep_lock' hack to
indicate Greg's non-NAK.
[1]: https://lore.kernel.org/lkml/156029554317.419799.1324389595953183385.stgi...
---
The libnvdimm subsystem uses async operations to parallelize device
probing operations and to allow sysfs to trigger device_unregister() on
deleted namepsaces. A multithreaded stress test of the libnvdimm sysfs
interface uncovered a case where device_unregister() is triggered
multiple times, and the subsequent investigation uncovered a broken
locking scenario.
The lack of lockdep coverage for device_lock() stymied the debug. That
is, until patch6 "driver-core, libnvdimm: Let device subsystems add
local lockdep coverage" solved that with a shadow lock, with lockdep
coverage, to mirror device_lock() operations. Given the time saved with
shadow-lock debug-hack, patch6 attempts to generalize device_lock()
debug facility that might be able to be carried upstream. Patch6 is
staged at the end of this fix series in case it is contentious and needs
to be dropped.
Patch1 "drivers/base: Introduce kill_device()" could be achieved with
local libnvdimm infrastructure. However, the existing 'dead' flag in
'struct device_private' aims to solve similar async register/unregister
races so the fix in patch2 "libnvdimm/bus: Prevent duplicate
device_unregister() calls" can be implemented with existing driver-core
infrastructure.
Patch3 is a rare lockdep warning that is intermittent based on
namespaces racing ahead of the completion of probe of their parent
region. It is not related to the other fixes, it just happened to
trigger as a result of the async stress test.
Patch5 and patch6 address an ABBA deadlock tripped by the stress test.
These patches pass the failing stress test and the existing libnvdimm
unit tests with CONFIG_PROVE_LOCKING=y and the new "dev->lockdep_mutex"
shadow lock with no lockdep warnings.
---
Dan Williams (7):
drivers/base: Introduce kill_device()
libnvdimm/bus: Prevent duplicate device_unregister() calls
libnvdimm/region: Register badblocks before namespaces
libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
libnvdimm/bus: Stop holding nvdimm_bus_list_mutex over __nd_ioctl()
libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
driver-core, libnvdimm: Let device subsystems add local lockdep coverage
drivers/acpi/nfit/core.c | 28 +++--
drivers/acpi/nfit/nfit.h | 24 ++++
drivers/base/core.c | 30 ++++--
drivers/nvdimm/btt_devs.c | 16 +--
drivers/nvdimm/bus.c | 210 ++++++++++++++++++++++++++-------------
drivers/nvdimm/core.c | 10 +-
drivers/nvdimm/dimm_devs.c | 4 -
drivers/nvdimm/namespace_devs.c | 36 +++----
drivers/nvdimm/nd-core.h | 71 +++++++++++++
drivers/nvdimm/pfn_devs.c | 24 ++--
drivers/nvdimm/pmem.c | 4 -
drivers/nvdimm/region.c | 24 ++--
drivers/nvdimm/region_devs.c | 12 +-
include/linux/device.h | 6 +
14 files changed, 343 insertions(+), 156 deletions(-)
2 years, 11 months
[GIT PULL] dax for 5.3
by Dan Williams
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/dax-for-5.3
...to receive the fruits of a bug hunt in the fsdax implementation
with Willy and a small feature update for device-dax. These have
appeared in a -next release with no reported issues.
---
The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/dax-for-5.3
for you to fetch changes up to 23c84eb7837514e16d79ed6d849b13745e0ce688:
dax: Fix missed wakeup with PMD faults (2019-07-16 19:30:59 -0700)
----------------------------------------------------------------
- Fix a hang condition that started triggering after the Xarray
conversion of fsdax in the v4.20 kernel.
- Add a 'resource' (root-only physical base address) sysfs attribute to
device-dax instances to correlate memory-blocks onlined via the kmem
driver with a given device instance.
----------------------------------------------------------------
Matthew Wilcox (Oracle) (1):
dax: Fix missed wakeup with PMD faults
Vishal Verma (1):
device-dax: Add a 'resource' attribute
drivers/dax/bus.c | 19 +++++++++++++++++++
fs/dax.c | 53 +++++++++++++++++++++++++++++++++--------------------
2 files changed, 52 insertions(+), 20 deletions(-)
2 years, 11 months
