Hi Tejun,
Any comments about this?
Thanks
On 2017/9/27 17:17, tanxiaofei wrote:
>
>
> On 2017/9/25 23:25, Tejun Heo wrote:
>> Hello,
>>
>> On Sat, Sep 23, 2017 at 05:04:24PM +0800, tanxiaofei wrote:
>>> Hi Tejun & Jiangshan,
>>>
>>> I find an null pointer risk in the code of workqueue. Here is
On Thu, Oct 19, 2017 at 03:44:31PM -0700, Darrick J. Wong wrote:
> > > The code looks fine, but this seems really strange. If the trylock
> > > fails, then wouldn't the blocking lock have slept anyways if done
> > > initially? Is there any more background info available on this, or
> > > perhaps a
On Thu, Oct 19, 2017 at 08:28:04PM -0500, Josh Poimboeuf wrote:
> On Thu, Oct 19, 2017 at 03:35:22PM -0700, Andrei Vagin wrote:
> > On Thu, Oct 19, 2017 at 01:16:55PM -0500, Josh Poimboeuf wrote:
> > > On Thu, Oct 19, 2017 at 09:51:04AM -0700, Andrei Vagin wrote:
> > > > Hi,
> > > >
> > > > We run
On Fri, Oct 20, 2017 at 8:29 AM, Ross Zwisler
wrote:
> Add a test that exercises DAX's new MAP_SYNC flag.
>
> This test creates a file and writes to it via an mmap(), but never syncs
> via fsync/msync. This process is tracked via dm-log-writes, then replayed.
>
> If MAP_SYNC is working the dm-log
A release candidate Git v2.15.0-rc2 is now available for testing
at the usual places. It is comprised of 737 non-merge commits
since v2.14.0, contributed by 75 people, 22 of which are new faces.
We had to back-track a bit wrt to the "git add -p" regression; for
now, we simply revert the changes t
On Thu, Oct 19, 2017 at 03:52:41PM +0100, David Howells wrote:
> From: Linn Crosetto
>
> ACPI provides an error injection mechanism, EINJ, for debugging and testing
> the ACPI Platform Error Interface (APEI) and other RAS features. If
> supported by the firmware, ACPI specification 5.0 and later
On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote:
> On Fri 20-10-17 11:13:29, Joonsoo Kim wrote:
> > On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote:
> > > On Thu 19-10-17 10:20:41, Michal Hocko wrote:
> > > > On Thu 19-10-17 16:33:56, Joonsoo Kim wrote:
> > > > > On Thu, O
Hi Vlastimil,
Thanks for your comment!
On 2017/10/18 18:46, Vlastimil Babka wrote:
> On 10/18/2017 11:34 AM, Yisheng Xie wrote:
For MAX_NUMNODES is 4, so 0x10 nodemask will tread as empty set which makes
nodes_subset(*new, node_states[N_MEMORY])
>>>
>>> According to manpage of migrate
On 20/10/2017 00:25, Thomas Gleixner wrote:
> On Fri, 20 Oct 2017, Daniel Lezcano wrote:
>
>> On 19/10/2017 22:57, David Kozub wrote:
>>> This solves a BUG on ALIX 2c3 where mfgpt_tick is called before
>>> clockevents_config_and_register returns. This caused mfgpt_tick to call a
>>> null function
On Thu, Oct 19, 2017 at 03:52:34PM +0100, David Howells wrote:
> From: Linn Crosetto
>
> >From the kernel documentation (initrd_table_override.txt):
>
> If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
> to override nearly any ACPI table provided by the BIOS with an
>
On Thu, Oct 19, 2017 at 03:52:27PM +0100, David Howells wrote:
> From: Josh Boyer
>
> This option allows userspace to pass the RSDP address to the kernel, which
> makes it possible for a user to modify the workings of hardware . Reject
> the option when the kernel is locked down.
>
> Signed-off
On Thu, Oct 19, 2017 at 03:52:19PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> custom_method effectively allows arbitrary access to system memory, making
> it possible for an attacker to circumvent restrictions on module loading.
> Disable it if the kernel is locked down.
>
> Signed-
On Thu, Oct 19, 2017 at 03:52:11PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> We have no way of validating what all of the Asus WMI methods do on a given
> machine - and there's a risk that some will allow hardware state to be
> manipulated in such a way that arbitrary code can be ex
On Thu, Oct 19, 2017 at 03:52:04PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> Writing to MSRs should not be allowed if the kernel is locked down, since
> it could lead to execution of arbitrary code in kernel mode. Based on a
> patch by Kees Cook.
>
> Signed-off-by: Matthew Garrett
On Thu, Oct 19, 2017 at 03:51:56PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> IO port access would permit users to gain access to PCI configuration
> registers, which in turn (on a lot of hardware) give access to MMIO
> register space. This would potentially permit root to trigger ar
On Thu, Oct 19, 2017 at 03:51:49PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> Any hardware that can potentially generate DMA has to be locked down in
> order to avoid it being possible for an attacker to modify kernel code,
> allowing them to circumvent disabled module loading or mod
Hi Chao,
[...]
Thanks for that. I think likely() is suitable for another place.
Aha, Just as an example, don't need to use it. ;-)
Both are OK. I think outputing the memory region in movable_node or
immovable_node are both reasonable. So the interface of both methods
will be useful. And af
On Thu, Oct 19, 2017 at 03:51:42PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> uswsusp allows a user process to dump and then restore kernel state, which
> makes it possible to modify the running kernel. Disable this if the kernel
> is locked down.
>
> Signed-off-by: Matthew Garrett
On Thu, Oct 19, 2017 at 03:51:34PM +0100, David Howells wrote:
> From: Josh Boyer
>
> There is currently no way to verify the resume image when returning
> from hibernate. This might compromise the signed modules trust model,
> so until we can work with signed hibernate images we disable it when
On Thu, Oct 19, 2017 at 03:51:20PM +0100, David Howells wrote:
> From: Dave Young
>
> Kexec reboot in case secure boot being enabled does not keep the secure
> boot mode in new kernel, so later one can load unsigned kernel via legacy
> kexec_load. In this state, the system is missing the protect
On Thu, Oct 19, 2017 at 03:51:09PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> kexec permits the loading and execution of arbitrary code in ring 0, which
> is something that lock-down is meant to prevent. It makes sense to disable
> kexec in this situation.
>
> This does not affect k
On Thu, 19 Oct 2017, Gayatri Kammela wrote:
> @@ -76,6 +76,12 @@ void fpu__xstate_clear_all_cpu_caps(void)
> setup_clear_cpu_cap(X86_FEATURE_XGETBV1);
Please rework this against:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/fpu
Thanks,
tglx
Hi David,
Thanks for you send out this series.
On Thu, Oct 19, 2017 at 03:51:02PM +0100, David Howells wrote:
> From: Matthew Garrett
>
> Allowing users to write to address space makes it possible for the kernel to
> be subverted, avoiding module loading restrictions. Prevent this when the
> k
On Thu, 19 Oct 2017, Bart Van Assche wrote:
> On Wed, 2017-10-18 at 18:38 +0900, Byungchul Park wrote:
> > Sometimes, we want to initialize completions with sparate lockdep maps
> > to assign lock classes under control. For example, the workqueue code
> > manages lockdep maps, as it can classify lo
> -Original Message-
> From: Lu Baolu [mailto:baolu...@linux.intel.com]
> Sent: Friday, October 20, 2017 8:49 AM
> To: Liu, Yi L ; j...@8bytes.org; dw...@infradead.org
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/3] iommu/vt-d: Missing check
On 20/10/2017 03:52, Eduardo Valentin wrote:
> On Thu, Oct 19, 2017 at 07:05:43PM +0200, Daniel Lezcano wrote:
>> The interrupt for the temperature threshold is not enabled at the end of the
>> probe function, enable it after the setup is complete.
>>
>> On the other side, the irq_enabled is not co
On 20.10.2017 08:31, Michal Simek wrote:
> On 18.10.2017 09:02, Kedareswara rao Appana wrote:
>> This patch adds runtime pm support in the driver.
>>
>> Signed-off-by: Kedareswara rao Appana
>> ---
>> drivers/dma/xilinx/zynqmp_dma.c | 167
>>
>> 1 file ch
Hi David,
Thanks for you send our this series.
On Thu, Oct 19, 2017 at 03:50:55PM +0100, David Howells wrote:
> If the kernel is locked down, require that all modules have valid
> signatures that we can verify.
>
> Signed-off-by: David Howells
I have reviewed and tested this patch. Please feel
On 18.10.2017 09:02, Kedareswara rao Appana wrote:
> This patch adds runtime pm support in the driver.
>
> Signed-off-by: Kedareswara rao Appana
> ---
> drivers/dma/xilinx/zynqmp_dma.c | 167
>
> 1 file changed, 135 insertions(+), 32 deletions(-)
>
> di
Brian Norris writes:
> Build errors have been reported with CONFIG_PM=n:
>
> drivers/net/wireless/ath/ath10k/pci.c:3416:8: error: implicit
> declaration of function 'ath10k_pci_suspend'
> [-Werror=implicit-function-declaration]
>
> drivers/net/wireless/ath/ath10k/pci.c:3428:8: error: implicit
> d
On Thu, Oct 19, 2017 at 05:18:45PM -0500, Tom Gall wrote:
>
> > On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman
> > wrote:
> >
> > This is the start of the stable review cycle for the 4.9.58 release.
> > There are 51 patches in this series, all will be posted as a response
> > to this one. If
On Thu, Oct 19, 2017 at 05:18:38PM -0500, Tom Gall wrote:
>
> > On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman
> > wrote:
> >
> > This is the start of the stable review cycle for the 4.4.94 release.
> > There are 46 patches in this series, all will be posted as a response
> > to this one. If
Brian Norris writes:
> + Arnd
>
> On Thu, Oct 19, 2017 at 02:32:45PM +, Kalle Valo wrote:
>> Kalle Valo writes:
>>
>> > Brian Norris wrote:
>> >
>> >> For devices where the FW supports WoWLAN but user-space has not
>> >> configured it, we don't do any PCI-specific suspend/resume operations
On Fri, Oct 20, 2017 at 03:22:07AM +0200, Rafael J. Wysocki wrote:
> On Friday, October 20, 2017 3:23:16 AM CEST Jeffy Chen wrote:
> > The current ordering of code in device_del() triggers a WARN_ON()
> > in device_links_purge(), because of an unexpected link status.
> >
> > The device_links_unbin
On Thu, Oct 19, 2017 at 12:50 AM, Qixuan Wu wrote:
> Hi All,
>
> Currently, squashfs fragments' cache size is only determined by
> config option CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE. Users have
> no way to change the value when they get the binary kernel.
Thank-you for the patches, but they're bot
On Thu 19-10-17 15:25:07, Shakeel Butt wrote:
> lru_add_drain_all() is not required by mlock() and it will drain
> everything that has been cached at the time mlock is called. And
> that is not really related to the memory which will be faulted in
> (and cached) and mlocked by the syscall itself.
>
From: Mohammed Gamal
Date: Tue, 17 Oct 2017 16:33:43 +0200
> Currently the vmxnet3 driver has a minimum MTU value of 60. Which
> goes against the RFC791 spec which specifies it at 68.
>
> Setting MTU to values between 60 <= MTU <= 67 causes the network
> interface to lose its IP, and it fails to
On Thu, Oct 19, 2017 at 11:24:00PM +, Bart Van Assche wrote:
> Are there any completion objects for which the cross-release checking is
> useful? Are there any wait_for_completion() callers that hold a mutex or
> other locking object?
Check /proc/lockdep, then you can find all dependencies wrt
On Thu, 2017-10-19 at 13:31 -0700, Michael Davidson wrote:
> int_sqrt() currently takes approximately constant time
> regardless of the value of the argument. By using the
> magnitude of the operand to set the initial conditions
> for the calculation the cost becomes proportional to
> log2 of the a
On Wed, Oct 04, 2017 at 02:37:23PM +0300, Alexander Kochetkov wrote:
> If two concurrent threads call pl330_get_desc() when DMAC descriptor
> pool is empty it is possible that allocation for one of threads will fail
> with message:
>
> kernel: dma-pl330 20078000.dma-controller: pl330_get_desc:2469
On Thu, Oct 19, 2017 at 01:15:13AM +, Kuninori Morimoto wrote:
> From: Hiroyuki Yokoyama
>
> SYS/RT/Audio DMAC includes independent data buffers for reading
> and writing. Therefore, the read transfer counter and write transfer
> counter have different values.
> TCR indicates read counter, an
On Wed, Oct 18, 2017 at 12:01:28AM +, Kuninori Morimoto wrote:
>
> Hi Vinod, Laurent
>
> > > > Anyway, in all case I can use TCRB in v3 patch,
> > > > and it needs abouve explanation.
> > >
> > > If so, I think v1 is enough... ?
> > > "transfer completed count is important for all case" is n
[...]
> In this regards as we consider genpd being a trivial PM domain, those
> examples your bring up above is too me also examples of trivial PM
> domains. Especially because they don't deal with wakeups, as that is
> taken care of by the drivers, right!?
Not directly,
Hi Chao,
At 10/20/2017 11:41 AM, Chao Fan wrote:
On Fri, Oct 20, 2017 at 11:17:26AM +0800, Dou Liyang wrote:
Hi Chao
Hi Dou-san,
At 10/19/2017 06:02 PM, Chao Fan wrote:
Since the interrelationship between e820 or efi entries and memory
region in immovable_mem is different:
One memory regio
On Thu, Oct 19, 2017 at 08:21:56PM +, Bart Van Assche wrote:
> * How much review has the Documentation/locking/crossrelease.txt received
> before it went upstream? At least to me that document seems much harder
> to read than other kernel documentation due to weird use of the English
> gr
On Fri 20-10-17 11:13:29, Joonsoo Kim wrote:
> On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote:
> > On Thu 19-10-17 10:20:41, Michal Hocko wrote:
> > > On Thu 19-10-17 16:33:56, Joonsoo Kim wrote:
> > > > On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote:
> > > > > On Thu 19
Hi Linus,
Standard fixes pull for rc6. One regression fix for amdgpu, a bunch
of nouveau fixes that I'd missed a pull req for from Ben last week,
some exynos regression fixes, and a few fixes for i915.
Dave.
The following changes since commit 33d930e59a98fa10a0db9f56c7fa2f21a4aef9b9:
Linux 4.1
On 20 October 2017 at 03:19, Rafael J. Wysocki wrote:
> On Thursday, October 19, 2017 2:21:07 PM CEST Ulf Hansson wrote:
>> On 19 October 2017 at 00:12, Rafael J. Wysocki wrote:
>> > On Wednesday, October 18, 2017 4:11:33 PM CEST Ulf Hansson wrote:
>> >> [...]
>> >>
>> >> >>
>> >> >> The reason w
Now crashkernel=X will fail if there's not enough memory at low region
(below 896M) when trying to reserve large memory size. One can use
crashkernel=xM,high to reserve it at high region (>4G) but it is more
convinient to improve crashkernel=X to:
- First try to reserve X below 896M (for being
The usage of of_device_get_match_data reduce the code size a bit.
Furthermore, it prevents an improbable dereference when
of_match_device() return NULL.
Signed-off-by: Corentin Labbe
---
drivers/iio/adc/sun4i-gpadc-iio.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/d
Hi Boris,
- boris.ostrov...@oracle.com wrote:
> On 10/19/2017 04:02 AM, Dongli Zhang wrote:
> > After guest live migration on xen, steal time in /proc/stat
> > (cpustat[CPUTIME_STEAL]) might decrease because steal returned by
> > xen_steal_lock() might be less than this_rq()->prev_steal_time
On Thu, Oct 19, 2017 at 8:13 PM, Wei Wei wrote:
> Sry. Here it is.
>
> Unable to handle kernel paging request at virtual address 80005bfb81ed
> Mem abort info:
> Exception class = DABT (current EL), IL = 32 bits
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> Data abort info:
> ISV = 0, ISS = 0x0
[...]
+#ifdef CONFIG_MEMORY_HOTPLUG
+static void mem_mark_immovable(char *str)
+{
+ int i = 0;
+
you have use num_immovable_region, 'i' is useless. just remove it.
Using num_immovable_region makes code too long. Using i will be
clear and make sure shoter than 80 characters.
Oh, God,
Add a test that exercises DAX's new MAP_SYNC flag.
This test creates a file and writes to it via an mmap(), but never syncs
via fsync/msync. This process is tracked via dm-log-writes, then replayed.
If MAP_SYNC is working the dm-log-writes replay will show the test file
with the same size that w
On Thu, Oct 19, 2017 at 11:13:48AM +0200, Takashi Iwai wrote:
> On Thu, 19 Oct 2017 05:03:22 +0200,
> Vinod Koul wrote:
> >
> > +static inline int find_error_code(unsigned int sdw_ret)
> > +{
> > + switch (sdw_ret) {
> > + case SDW_CMD_OK:
> > + return 0;
> > +
> > + case SDW_CMD_I
Currently dm-log-writes supports writing filesystem data via BIOs, and
writing internal metadata from a flat buffer via write_metadata().
For DAX writes, though, we won't have a BIO, but will instead have an
iterator that we'll want to use to fill a flat data buffer.
So, create write_inline_data(
Now that we have the ability log filesystem writes using a flat buffer, add
support for DAX. Unfortunately we can't easily track data that has been
written via mmap() now that the dax_flush() abstraction was removed by this
commit:
commit c3ca015fab6d ("dax: remove the pmem_dax_ops->flush abstrac
On Thu, Oct 19, 2017 at 11:02:02AM +0200, Takashi Iwai wrote:
> On Thu, 19 Oct 2017 05:03:20 +0200,
> Vinod Koul wrote:
> >
> > + slave->ops = drv->ops;
> > +
> > ret = drv->probe(slave, id);
> > if (ret) {
> > dev_err(dev, "Probe of %s failed: %d\n", drv->name, ret);
> >
Without the STDMAC clock enabled, the USB 2.0 hosts do not work.
This clock must be explicitly listed in the "clocks" property because
it is independent from the other clocks.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4.dtsi | 9 ++---
arch/arm/boot/dts/uniphier-pro4.
Without the STDMAC clock enabled, the USB 2.0 hosts do not work.
This clock must be explicitly listed in the "clocks" property because
it is independent from the other clocks.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 9 ++---
1 file changed, 6 in
On Thu, Oct 19, 2017 at 10:54:50AM +0200, Takashi Iwai wrote:
> On Thu, 19 Oct 2017 05:03:19 +0200,
> Vinod Koul wrote:
> > +int sdw_add_bus_master(struct sdw_bus *bus)
> > +{
> > + int ret;
> > +
> > + if (!bus->dev) {
> > + pr_err("SoundWire bus has no device");
> > + ret
On Thu, 19 Oct 2017, Richard Guy Briggs wrote:
> On 2017-10-11 20:57, Richard Guy Briggs wrote:
> > The audit subsystem is adding a BPRM_FCAPS record when auditing setuid
> > application execution (SYSCALL execve). This is not expected as it was
> > supposed to be limited to when the file system a
Hi Milian,
On Thu, Oct 19, 2017 at 12:54:18PM +0200, Milian Wolff wrote:
> On Mittwoch, 18. Oktober 2017 20:53:50 CEST Milian Wolff wrote:
> > When inline frame resolution is disabled, a bogus srcline is obtained
> > for hist entries:
> >
> > ~
> > $ perf report -s sym,srcline --no-inline --s
On Thu, Oct 19, 2017 at 09:40:06AM +0200, Takashi Iwai wrote:
> On Thu, 19 Oct 2017 05:03:18 +0200,
> Vinod Koul wrote:
> > +
> > +config SOUNDWIRE_BUS
> > + tristate
> > + default SOUNDWIRE
> > +
>
> Does it make sense to be tristate?
> Since CONFIG_SOUNDWIRE is a bool, the above would be als
On Fri 06 Oct 08:51 PDT 2017, srinivas.kandaga...@linaro.org wrote:
> diff --git a/drivers/base/regmap/regmap-slimbus.c
> b/drivers/base/regmap/regmap-slimbus.c
[..]
> +static int regmap_slimbus_byte_reg_read(void *context, unsigned int reg,
> + unsigned int *val)
> +{
> + struct slim_device *sli
On Wed 18 Oct 18:10 PDT 2017, Chris Lew wrote:
> Virtual GLINK channels may know what throughput to expect from a
> remoteproc. An intent advertises to the remoteproc this channel is
> ready to receive data. Allow a channel to define the size and amount of
> intents to be prequeued.
>
> Signed-off
Hi,
On Wed, Oct 18, 2017 at 9:45 AM, Masahiro Yamada
wrote:
> 2017-10-14 3:02 GMT+09:00 Douglas Anderson :
>> Right now there is a way to add some CFLAGS that affect target builds,
>> but no way to add CFLAGS that affect host builds. Let's add a way.
>> We'll document two environment variables:
On Fri 06 Oct 08:51 PDT 2017, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> Add myself as maintainer for slimbus.
>
Acked-by: Bjorn Andersson
Regards,
Bjorn
> Signed-off-by: Srinivas Kandagatla
> ---
> MAINTAINERS | 8
> 1 file changed, 8 insertions(+)
>
> d
On Wed 18 Oct 09:39 PDT 2017, Srinivas Kandagatla wrote:
> Thanks for Review Comments,
>
>
> On 18/10/17 07:15, Bjorn Andersson wrote:
> > On Fri 06 Oct 08:51 PDT 2017, srinivas.kandaga...@linaro.org wrote:
[..]
> >
> > > + if (!async) {
> > > + txn->msg->comp_cb = NULL;
> > > + txn->msg->ctx = NU
On 2017/10/12 22:26, Boris Brezillon wrote:
> On Thu, 12 Oct 2017 22:03:23 +0900
> KOBAYASHI Yoshitake wrote:
>
>> On 2017/10/05 16:31, Boris Brezillon wrote:
>>> On Thu, 5 Oct 2017 16:24:08 +0900
>>> KOBAYASHI Yoshitake wrote:
@@ -39,9 +105,43 @@ static void toshiba_nand_decode_id(st
Linus,
here are a couple of bugfixes for I2C drivers. Because the changes for
the piix4 driver are larger than usual, the patches have been in
linux-next for more than a week with no reports coming in. The rest is
usual stuff.
Please pull.
Thanks,
Wolfram
The following changes since commit
Hi, Matt,
I found that 4ee34ea3a12396f35b26d90a094c75db ("libata: Align ata_device's id
on a cacheline") can resolve everything. Because the size of id[ATA_ID_WORDS]
is already aligned and devslp_timing needn't to be aligned. So, In V9 of this
series I will drop this patch. Why I had problems b
On Fri, Oct 20, 2017 at 11:19:48AM +0800, Dou Liyang wrote:
>Hi Chao,
>
>At 10/19/2017 06:02 PM, Chao Fan wrote:
>> There are two same variable "rc" in this function. One is in the
>> circulation, the other is out of the circulation. The one out will never
>> be used, so drop it.
>>
>> Signed-off-
On 10/20/2017 12:10 AM, Huang, Ying wrote:
> From: Huang Ying
>
> Now, when the page table is walked in the implementation of
> /proc//pagemap, pmd_soft_dirty() is used for both the PMD huge
> page map and the PMD migration entries. That is wrong,
> pmd_swp_soft_dirty() should be used for the
On Fri, Oct 20, 2017 at 11:37:11AM +0800, Dou Liyang wrote:
>Hi Chao,
>
>At 10/20/2017 10:53 AM, Chao Fan wrote:
>> On Fri, Oct 20, 2017 at 10:37:52AM +0800, Dou Liyang wrote:
>> > Hi Chao,
>> >
>> Hi Dou-san,
>>
>> > Cheer! I have some concerns below.
>>
>> Thanks for your reply.
>>
>> >
>> >
On Fri, Oct 20, 2017 at 11:41:19AM +0800, Dou Liyang wrote:
>
>
>At 10/20/2017 11:22 AM, Chao Fan wrote:
>> On Fri, Oct 20, 2017 at 11:04:42AM +0800, Dou Liyang wrote:
>> > Hi Chao,
>> >
>> Hi Dou-san,
>>
>> > At 10/19/2017 06:02 PM, Chao Fan wrote:
>> > > Extend the movable_node to movable_node=
At 10/20/2017 11:22 AM, Chao Fan wrote:
On Fri, Oct 20, 2017 at 11:04:42AM +0800, Dou Liyang wrote:
Hi Chao,
Hi Dou-san,
At 10/19/2017 06:02 PM, Chao Fan wrote:
Extend the movable_node to movable_node=nn[KMG]@ss[KMG].
Since in current code, kaslr may choose the memory region in hot-plugga
On Fri, Oct 20, 2017 at 11:17:26AM +0800, Dou Liyang wrote:
>Hi Chao
>
Hi Dou-san,
>At 10/19/2017 06:02 PM, Chao Fan wrote:
>> Since the interrelationship between e820 or efi entries and memory
>> region in immovable_mem is different:
>> One memory region in one node may contain several entries of
Expose a new 'maintain' sysfs attribute to control both suspend and
reset tolerance.
Signed-off-by: Andrew Jeffery
---
Documentation/gpio/sysfs.txt | 9 +
drivers/gpio/gpiolib-sysfs.c | 88 ++--
2 files changed, 93 insertions(+), 4 deletions(-)
diff
Use the new pinconf parameter for reset tolerance to expose the
associated capability of the Aspeed GPIO controller.
Signed-off-by: Andrew Jeffery
---
drivers/gpio/gpio-aspeed.c | 39 +--
1 file changed, 37 insertions(+), 2 deletions(-)
diff --git a/drivers/g
Similar to devicetree support, add flags and mappings to expose reset
tolerance configuration through the chardev interface.
Signed-off-by: Andrew Jeffery
---
drivers/gpio/gpiolib.c| 14 +-
include/uapi/linux/gpio.h | 11 ++-
2 files changed, 19 insertions(+), 6 deletions
Add flags and the associated flag mappings between interfaces to enable
GPIO reset tolerance to be specified via devicetree.
Signed-off-by: Andrew Jeffery
---
drivers/gpio/gpiolib-of.c | 2 ++
drivers/gpio/gpiolib.c | 5 +
include/dt-bindings/gpio/gpio.h | 4
include/linu
GPIO state reset tolerance is implemented in gpiolib through the
addition of a new pinconf parameter. With that, some renaming of helpers
is done to clarify the scope of the already existing
gpiochip_line_is_persistent(), as it's now ambiguous as to whether that
means on suspend, reset or both. Thi
Hello,
This series exposes a "reset tolerant" property for GPIOs. For example, the
controller implemented in Aspeed BMCs provides such a feature to allow the BMC
to be reset whilst maintaining necessary state to keep host systems alive or
status LEDs in-tact.
I'm sending it as an RFC because I'm
Hi Chao,
At 10/20/2017 10:53 AM, Chao Fan wrote:
On Fri, Oct 20, 2017 at 10:37:52AM +0800, Dou Liyang wrote:
Hi Chao,
Hi Dou-san,
Cheer! I have some concerns below.
Thanks for your reply.
At 10/19/2017 06:02 PM, Chao Fan wrote:
Here is a problem:
Here is a machine with several NUMA no
On Fri, Oct 20, 2017 at 11:41:17AM +1100, NeilBrown wrote:
> On Wed, Aug 02 2017, NeilBrown wrote:
>
> > Many of the inlines in dcache.h were changed to accept
> > const struct pointers in commit f0d3b3ded999 ("constify dcache.c
> > inlined helpers where possible").
> > This patch allows 'const' i
On Fri, Oct 20, 2017 at 11:04:42AM +0800, Dou Liyang wrote:
>Hi Chao,
>
Hi Dou-san,
>At 10/19/2017 06:02 PM, Chao Fan wrote:
>> Extend the movable_node to movable_node=nn[KMG]@ss[KMG].
>> Since in current code, kaslr may choose the memory region in hot-pluggable
>> nodes. So we can specific the re
Hi Chao,
At 10/19/2017 06:02 PM, Chao Fan wrote:
There are two same variable "rc" in this function. One is in the
circulation, the other is out of the circulation. The one out will never
be used, so drop it.
Signed-off-by: Chao Fan
---
arch/x86/boot/compressed/kaslr.c | 5 ++---
1 file change
Hi Chao
At 10/19/2017 06:02 PM, Chao Fan wrote:
Since the interrelationship between e820 or efi entries and memory
region in immovable_mem is different:
One memory region in one node may contain several entries of e820 or
efi sometimes, and one entry of e820 or efi may contain the memory in
diff
On Fri, Oct 20, 2017 at 12:20 AM, Yang Shi wrote:
> We observed some misbehaved user applications might consume significant
> amount of fsnotify slabs silently. It'd better to account those slabs in
> kmemcg so that we can get heads up before misbehaved applications use too
> much memory silently.
Sry. Here it is.
Unable to handle kernel paging request at virtual address 80005bfb81ed
Mem abort info:
Exception class = DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
Data abort info:
ISV = 0, ISS = 0x0033
CM = 0, WnR = 0
swapper pgtable: 4k pages, 48-bit VAs, pgd = f
Hi Chao,
At 10/19/2017 06:02 PM, Chao Fan wrote:
Extend the movable_node to movable_node=nn[KMG]@ss[KMG].
Since in current code, kaslr may choose the memory region in hot-pluggable
nodes. So we can specific the region in immovable node. And store the
regions in immovable_mem.
I guess you may
Literally.
I expect "lose" was meant here, rather than "loose", though you could feasibly
use a somewhat uncommon definition of "loose" to mean what would be meant by
"lose": "Loose the hounds" for instance, as in "Release the hounds".
Substituting in "value" for "hounds" gives "release the value"
On Fri, Oct 20, 2017 at 10:37:52AM +0800, Dou Liyang wrote:
>Hi Chao,
>
Hi Dou-san,
>Cheer! I have some concerns below.
Thanks for your reply.
>
>At 10/19/2017 06:02 PM, Chao Fan wrote:
>> Here is a problem:
>> Here is a machine with several NUMA nodes and some of them are hot-pluggable.
>> It's
On Thu, Oct 19, 2017 at 7:16 PM, Wei Wei wrote:
> Hi all,
>
> I have fuzzed v4.14-rc3 using syzkaller and found a bug similar to that one
> [1].
> But the call trace isnโt the same. The atomic_inc() might handle a corrupted
> skb_buff.
>
> The logs and config have been uploaded to my github repo
This part of Secure Encryted Virtualization (SEV) patch series focuses on KVM
changes required to create and manage SEV guests.
SEV is an extension to the AMD-V architecture which supports running encrypted
virtual machine (VMs) under the control of a hypervisor. Encrypted VMs have
their
pages (c
From: Tom Lendacky
Update the CPU features to include identifying and reporting on the
Secure Encrypted Virtualization (SEV) feature. SEV is identified by
CPUID 0x801f, but requires BIOS support to enable it (set bit 23 of
MSR_K8_SYSCFG and set bit 0 of MSR_K7_HWCR). Only show the SEV featu
From: Tom Lendacky
Currently the nested_ctl variable in the vmcb_control_area structure is
used to indicate nested paging support. The nested paging support field
is actually defined as bit 0 of the field. In order to support a new
feature flag the usage of the nested_ctl and nested paging suppor
If hardware supports memory encryption then KVM_MEMORY_ENCRYPT_REG_REGION
and KVM_MEMORY_ENCRYPT_UNREG_REGION ioctl's can be used by userspace to
register/unregister the guest memory regions which may contain the encrypted
data (e.g guest RAM, PCI BAR, SMRAM etc).
Cc: Thomas Gleixner
Cc: Ingo Mol
Changes since v2 [1]:
* Add 'dax: handle truncate of dma-busy pages' which builds on the
removal of page-less dax to fix a latent bug handling dma vs truncate.
* Disable get_user_pages_fast() for dax
* Disable RDMA memory registrations against filesystem-DAX mappings for
non-ODP (On Demand Pagi
1 - 100 of 1278 matches
Mail list logo
