[PATCH] doc: nvdimm: remove reference to non-existent CONFIG_NFIT_TEST

The test driver is in tools/testing/nvdimm and cannot be selected by a config option. Signed-off-by: Michal Suchanek --- Documentation/driver-api/nvdimm/nvdimm.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/driver-api/nvdimm/nvdimm.rst

Re: [PATCH v3] mm/memory_hotplug: refrain from adding memory into an impossible node

On Wed, 2020-04-15 at 12:43 +0200, Michal Hocko wrote: > On Tue 14-04-20 17:58:12, Vishal Verma wrote: > [...] > > +static int check_hotplug_node(int nid) > > +{ > > + int alt_nid; > > + > > + if (node_possible(nid)) > > + return nid; > > + > > + alt_nid =

专业定制各行各业数据

专业定制各行各业数据 2020年香港企业名录100万物流行业邮箱数据大全126届广交会参展商名录126届广交会采购商名录2020年阿里巴巴国际站数据2018-2019年全国展会名录1000万邮箱数据大全1.5万张国外采购商名片 通過QQ或者E-mail咨詢 Q Q : 2083925785 E-mail: sales0...@hotmail.com ___ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe

Re: [PATCH 20/20] fuse,virtiofs: Add logic to free up a memory range

On Tue, Apr 14, 2020 at 03:30:45PM -0400, Vivek Goyal wrote: > On Sat, Mar 28, 2020 at 06:06:06AM +0800, Liu Bo wrote: > > On Fri, Mar 27, 2020 at 10:01:14AM -0400, Vivek Goyal wrote: > > > On Thu, Mar 26, 2020 at 08:09:05AM +0800, Liu Bo wrote: > > > > > > [..] > > > > > +/* > > > > > + * Find

[PATCH AUTOSEL 4.9 20/21] libnvdimm: Out of bounds read in __nd_ioctl()

From: Dan Carpenter [ Upstream commit f84afbdd3a9e5e10633695677b95422572f920dc ] The "cmd" comes from the user and it can be up to 255. It it's more than the number of bits in long, it results out of bounds read when we check test_bit(cmd, _mask). The highest valid value for "cmd" is

[PATCH AUTOSEL 4.14 29/30] libnvdimm: Out of bounds read in __nd_ioctl()

From: Dan Carpenter [ Upstream commit f84afbdd3a9e5e10633695677b95422572f920dc ] The "cmd" comes from the user and it can be up to 255. It it's more than the number of bits in long, it results out of bounds read when we check test_bit(cmd, _mask). The highest valid value for "cmd" is

Coral Sky General Trading L.L.C[Urgent Order]

___ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-le...@lists.01.org

[PATCH AUTOSEL 4.19 38/40] libnvdimm: Out of bounds read in __nd_ioctl()

From: Dan Carpenter [ Upstream commit f84afbdd3a9e5e10633695677b95422572f920dc ] The "cmd" comes from the user and it can be up to 255. It it's more than the number of bits in long, it results out of bounds read when we check test_bit(cmd, _mask). The highest valid value for "cmd" is

[PATCH AUTOSEL 5.4 81/84] libnvdimm: Out of bounds read in __nd_ioctl()

From: Dan Carpenter [ Upstream commit f84afbdd3a9e5e10633695677b95422572f920dc ] The "cmd" comes from the user and it can be up to 255. It it's more than the number of bits in long, it results out of bounds read when we check test_bit(cmd, _mask). The highest valid value for "cmd" is

[PATCH AUTOSEL 5.4 82/84] acpi/nfit: improve bounds checking for 'func'

From: Dan Carpenter [ Upstream commit 01091c496f920e634ea84b689f480c39016752a8 ] The 'func' variable can come from the user in the __nd_ioctl(). If it's too high then the (1 << func) shift in acpi_nfit_clear_to_send() is undefined. In acpi_nfit_ctl() we pass 'func' to test_bit(func, _mask)

[PATCH AUTOSEL 5.5 103/106] acpi/nfit: improve bounds checking for 'func'

From: Dan Carpenter [ Upstream commit 01091c496f920e634ea84b689f480c39016752a8 ] The 'func' variable can come from the user in the __nd_ioctl(). If it's too high then the (1 << func) shift in acpi_nfit_clear_to_send() is undefined. In acpi_nfit_ctl() we pass 'func' to test_bit(func, _mask)

[PATCH AUTOSEL 5.5 102/106] libnvdimm: Out of bounds read in __nd_ioctl()

From: Dan Carpenter [ Upstream commit f84afbdd3a9e5e10633695677b95422572f920dc ] The "cmd" comes from the user and it can be up to 255. It it's more than the number of bits in long, it results out of bounds read when we check test_bit(cmd, _mask). The highest valid value for "cmd" is

[PATCH AUTOSEL 5.6 124/129] libnvdimm: Out of bounds read in __nd_ioctl()

From: Dan Carpenter [ Upstream commit f84afbdd3a9e5e10633695677b95422572f920dc ] The "cmd" comes from the user and it can be up to 255. It it's more than the number of bits in long, it results out of bounds read when we check test_bit(cmd, _mask). The highest valid value for "cmd" is

[PATCH AUTOSEL 5.6 125/129] acpi/nfit: improve bounds checking for 'func'

From: Dan Carpenter [ Upstream commit 01091c496f920e634ea84b689f480c39016752a8 ] The 'func' variable can come from the user in the __nd_ioctl(). If it's too high then the (1 << func) shift in acpi_nfit_clear_to_send() is undefined. In acpi_nfit_ctl() we pass 'func' to test_bit(func, _mask)

Re: [PATCH v3] mm/memory_hotplug: refrain from adding memory into an impossible node

On Tue 14-04-20 17:58:12, Vishal Verma wrote: [...] > +static int check_hotplug_node(int nid) > +{ > + int alt_nid; > + > + if (node_possible(nid)) > + return nid; > + > + alt_nid = numa_map_to_online_node(nid); > + if (alt_nid == NUMA_NO_NODE) > + alt_nid =

Re: [PATCH v2] dax: Add missing annotation for wait_entry_unlocked()

On Wed 01-04-20 16:33:59, Jules Irenge wrote: > Sparse reports a warning at wait_entry_unlocked() > > warning: context imbalance in wait_entry_unlocked() - unexpected unlock > > The root cause is the missing annotation at wait_entry_unlocked() > Add the missing __releases(xas->xa->xa_lock)

Re: [PATCH v3] mm/memory_hotplug: refrain from adding memory into an impossible node

On 15.04.20 09:39, David Hildenbrand wrote: > On 15.04.20 01:58, Vishal Verma wrote: >> A misbehaving qemu created a situation where the ACPI SRAT table >> advertised one fewer proximity domains than intended. The NFIT table did >> describe all the expected proximity domains. This caused the

Re: [PATCH v3] mm/memory_hotplug: refrain from adding memory into an impossible node

On 15.04.20 01:58, Vishal Verma wrote: > A misbehaving qemu created a situation where the ACPI SRAT table > advertised one fewer proximity domains than intended. The NFIT table did > describe all the expected proximity domains. This caused the device dax > driver to assign an impossible