.snip..
> >
> > Acked-by: Roger Pau Monné
>
> Forgot to add, this needs to be backported to stable branches, so:
Annie, could you resend the patch with the tags and an update
to the description to me please?
>
> Cc: sta...@vger.kernel.org
>
> Roger.
>
> __
On Wed, Aug 23, 2017 at 1:43 PM, Paolo Bonzini wrote:
> Setting the VMCS12 to launched and clearing the vm_entry_intr_info_field
> was done as part of L0->L1 exit in prepare_vmcs12. In order to simplify
> prepare_vmcs12, move this to enter_vmx_non_root_mode since at this point
> we've already com
The host pkru is restored right after vcpu exit (commit 1be0e61), so
KVM_GET_XSAVE will return the host PKRU value instead. Fix this by
using the guest PKRU explicitly in fill_xsave and load_xsave. This
part is based on a patch by Junkang Fu.
The host PKRU data may also not match the value in vc
The host pkru is restored right after vcpu exit (commit 1be0e61), so
KVM_GET_XSAVE will return the host PKRU value instead. In general,
the PKRU value in vcpu->arch.guest_fpu.state cannot be trusted.
The first patch removes an unnecessary abstraction. The second
fixes the bug.
Please test the p
Move it to struct kvm_arch_vcpu, replacing guest_pkru_valid with a
simple comparison against the host value of the register.
Signed-off-by: Paolo Bonzini
---
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/kvm_cache_regs.h | 5 -
arch/x86/kvm/mmu.h | 2 +-
arch/x86/kvm/
From: Rafael J. Wysocki
Move the polling state initialization code to a separate file built
conditionally on CONFIG_ARCH_HAS_CPU_RELAX to get rid of the #ifdef
in driver.c.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpuidle/Makefile |1 +
drivers/cpuidle/driver.c | 31 -
Hi,
On x86 the fist idle state is a polling one, but the way it is set up is far
from straightforward and then it is avoided by governors in rather somewhat
convoluted fashion.
Make this more clear by explicitly flagging that state as "polling" and
checking its flag where it needs to be avoided i
From: Rafael J. Wysocki
Make the drivers that want to include the polling state into their
states table initialize it explicitly and drop the initialization of
it (which in fact is conditional, but that is not obvious from the
code) from the core.
Signed-off-by: Rafael J. Wysocki
---
drivers/a
From: Rafael J. Wysocki
On some architectures the first (index 0) idle state is a polling
one and it doesn't really save energy, so there is the
CPUIDLE_DRIVER_STATE_START symbol allowing some pieces of
cpuidle code to avoid using that state.
However, this makes the code rather hard to follow.
On Wed, Aug 23, 2017 at 12:56:10AM -0400, Sinan Kaya wrote:
> Sporadic reset issues have been observed with Intel 750 NVMe drive while
> assigning the physical function to the guest machine. The sequence of
> events observed is as follows:
>
> - perform a Function Level Reset (FLR)
> - sleep
A guest may not be configured to support RDRAND, even when the host
does. If the guest does not support RDRAND, intercept the instruction
and synthesize #UD. Also clear the "allowed-1" bit for RDRAND exiting
in the IA32_VMX_PROCBASED_CTLS2 MSR.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/vmx.c
Hi Brendan,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.13-rc6 next-20170823]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Brendan-Higgins/arm-npcm-add-basic
On 23/08/2017 23:25, Jim Mattson wrote:
>> + if (from_vmentry) {
>> + vmcs12->launch_state = 1;
> Because we defer most guest state validity checks to the hardware
> vmlaunch of the vmcs02, it is too early to set the vmcs12 launched
> state here. If the exit reason has the high
Pavel,
> > I'll forward your email to our support.
> > AFAIK, KSZ8895 has different register mapping from KSZ9477,
> > it will be more than ID changes in current driver.
>
> More than ID changes, indeed. As layout is completely different, it
> looks like different source file will be needed for s
On 8/23/2017 5:38 PM, Bjorn Helgaas wrote:
> If we increase the timeout, is there still value in adding the
> pci_bus_wait_crs() stuff? I'm not sure there is.
I agree increasing the timeout is more than enough for FLR case.
However, I was considering the wait and pending functions as a utility
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 2acf097f16abba684012cca670a61d94178bd1ab
commit: dd55d44f408419278c00887bfcb2261d0caae350 staging: vboxvideo: Add
vboxvideo to drivers/staging
date: 5 weeks ago
config: x86_64-randconfig-v0-08240305 (attac
Currently, the IRQs are disabled when the rtc character device is closed.
This means that the device needs to stay open to get alarms while the usual
use case will open the device, set the alarm and close the device as is
done in rtcwake.
Keep the alarm functional on character device release so th
On Wed, Aug 23, 2017 at 8:25 AM, Boqun Feng wrote:
> There is no need to use COMPLETION_INITIALIZER_ONSTACK() in
> acpi_nfit_flush_probe(), replace it with init_completion().
Now that I see the better version of this patch with the improved
changelog in the -mm tree...
Acked-by: Dan Williams
On Wed, 23 Aug 2017 20:41:59 +1000 Stephen Rothwell
wrote:
> After merging the akpm-current tree, today's linux-next build (mips
> defconfig) failed like this:
>
> In file included from include/linux/selection.h:11:0,
> from drivers/video/console/newport_con.c:16:
> include/lin
On Wed, Aug 23, 2017 at 01:52:35PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> If madvise(..., MADV_FREE) split a transparent hugepage, it called
> put_page() before unlock_page(). This was wrong because put_page() can
> free the page, e.g. if a concurrent madvise(..., MADV_DONTNEED) has
Commit aba831a69632 ("xen: remove tests for pvh mode in pure pv paths")
removed XENFEAT_auto_translated_physmap test in xen_alloc_p2m_entry()
since it is assumed that the routine is never called by non-PV guests.
However, alloc_xenballooned_pages() may make this call on a PVH guest.
Prevent this f
On Wed, Aug 23, 2017 at 05:51:19PM -0400, Sinan Kaya wrote:
> On 8/23/2017 5:38 PM, Bjorn Helgaas wrote:
> > If we increase the timeout, is there still value in adding the
> > pci_bus_wait_crs() stuff? I'm not sure there is.
>
> I agree increasing the timeout is more than enough for FLR case.
I
Hello Al,
When I analyzed the block layer core with sparse I noticed that the declaration
of copy_in_user() and also that of a pointer in compat_hdio_ioctl() are wrong.
Please consider these two patches for kernel v4.14.
Thanks,
Bart.
Bart Van Assche (2):
: Fix copy_in_user() declaration
co
copy_in_user() copies data from user-space address @from to user-
space address @to. Hence declare both @from and @to as user-space
pointers.
Fixes: commit d597580d3737 ("generic ...copy_..._user primitives")
Signed-off-by: Bart Van Assche
Cc:
---
include/linux/uaccess.h | 2 +-
1 file changed,
This patch avoids that sparse reports the following warning messages:
block/compat_ioctl.c:85:11: warning: incorrect type in assignment (different
address spaces)
block/compat_ioctl.c:85:11:expected unsigned long *[noderef] p
block/compat_ioctl.c:85:11:got void [noderef] *
block/compat_io
On 8/15/14 5:29 AM, Al Viro wrote:
> On Thu, Aug 14, 2014 at 07:58:56PM -0700, Luis R. Rodriguez wrote:
>
>> Christoph had noted that this seemed associated to the problem
>> that the btrfs uses different assignments for st_dev than s_dev,
>> but much as I'd like to see that changed based on discu
[stupid google spam filtered _this_ as spam, I don't know why]
On Wed, Aug 23, 2017 at 10:28:28AM +0100, Mark Brown wrote:
> On Tue, Aug 22, 2017 at 09:51:46PM -0400, Tom Rini wrote:
>
> > Not all devices with ACPI and this combination of sound devices will
> > have the required information provi
On Wed, Aug 23, 2017 at 08:27:18PM +, Linus Torvalds wrote:
> On Wed, Aug 23, 2017 at 12:59 PM, Kirill A. Shutemov
> wrote:
> >
> > In this case we need performance numbers for !PARAVIRT kernel.
>
> Yes.
>
> > Numbers for tight loop of "mmap(MAP_POPULATE); munmap()" might be
> > interesting
On 08/11, Sylwester Nawrocki wrote:
>
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
> Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/snawrocki/clk.git
> tags/clk-v4
Silence the sparse warning
clk/rockchip/clk.c:172:6: warning: symbol 'rockchip_fractional_approximation'
was not declared. Should it be static?
Cc: Elaine Zhang
Cc: Heiko Stuebner
Signed-off-by: Stephen Boyd
---
drivers/clk/rockchip/clk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Changed dev_err() call to use function name constant instead of hardcoded
string. Issue found by checkpatch.
Signed-off-by: Bryan Garza
---
drivers/staging/comedi/comedi_fops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/comedi_fops.c
b/drivers/sta
There are no checks for dma mapping errors in pch_udc.
Tha patch adds the checks and error handling code.
Compile tested only.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/usb/gadget/udc/pch_udc.c | 15 +--
1 file chang
On Wed, Aug 23, 2017 at 06:35:24PM -0400, Tom Rini wrote:
> After looking at 89128534f925 (which introduced the above line, and thus
Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read
From: Colin Ian King
Trivial fix to spelling mistake in MODULE_PARM_DESC text
Signed-off-by: Colin Ian King
---
sound/oss/pss.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/oss/pss.c b/sound/oss/pss.c
index 33c3a442e162..951b14dec73a 100644
--- a/sound/oss/pss.c
++
On 08/22, Bhumika Goyal wrote:
> Make these const as they are only stored in the const field of a
> clk_init_data structure.
>
> Signed-off-by: Bhumika Goyal
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On Wed, Aug 23, 2017 at 11:47:52PM +0100, Mark Brown wrote:
> On Wed, Aug 23, 2017 at 06:35:24PM -0400, Tom Rini wrote:
>
> > After looking at 89128534f925 (which introduced the above line, and thus
>
> Please include human readable descriptions of things like commits and
> issues being discussed
On 08/18, Georgi Djakov wrote:
> The clock bimc_gpu_clk_src is incorrectly set to use the shared rcg2
> ops, which are for RCGs with child branches controlled by different
> CPUs.
>
> The result of the incorrect ops is that the GPU's PM runtime may leave
> this clock set at a very low rate. Fix th
On Mon, 2017-08-21 at 08:23 -0700, Andy Lutomirski wrote:
>
> > On Aug 21, 2017, at 7:08 AM, Peter Zijlstra wrote:
> >
> >> On Mon, Aug 21, 2017 at 06:56:01AM -0700, Andy Lutomirski wrote:
> >>
> >>
> >>> On Aug 21, 2017, at 3:33 AM, Peter Zijlstra wrote:
> >
>
> Using a kernel th
- Original Message -
> From: "Steven Rostedt"
> To: "Chunyu Hu"
> Cc: mi...@kernel.org, linux-kernel@vger.kernel.org
> Sent: Wednesday, August 23, 2017 12:52:49 PM
> Subject: Re: [PATCH 2/2] tracing: Fix kmemleak in set_trigger_filter
>
> On Wed, 23 Aug 2017 10:41:55 -0400
> Steven Ros
On Wed, Aug 23, 2017 at 11:47:52PM +0100, Mark Brown wrote:
> > support for the Chromebook), I think that 36afb0ab648 and 55e59aa0525a
> > are wrong and should be reverted. It seems like they're an attempt to
> > make 89128534f925 be done 'properly' but it also seems like the
> Please be more sp
On Wed, Aug 23, 2017 at 04:26:00PM +0530, Sandeep Singh wrote:
> From: Sandeep Singh
>
> The following commit cause a regression on ATI chipsets.
> 'commit e788787ef4f9 ("usb:xhci:Add quirk for Certain
> failing HP keyboard on reset after resume")'
>
> This causes pinfo->smbus_dev to be wrongly
On Wed, Aug 23, 2017 at 3:36 PM, Kirill A. Shutemov
wrote:
>
> Below is test cases that allocates a lot of page tables and measuare
> fork/exit time. (I'm not entirely sure it's the best way to stress the
> codepath.)
Looks ok to me. Doing a profile (without the RCU freeing, obviously) gives me
The ghes_edac driver was introduced in 2013 [1], but it has not
been enabled by any distro yet. This driver obtains error info
from firmware interfaces, which are not properly implemented on
many platforms, as the driver always emits the messages below:
This EDAC driver relies on BIOS to enumera
Change generic x86 edac drivers, which probe CPU type with
x86_match_cpu(), to verify the module owner at the beginning
of their module init functions. This allows them to fail
their init immediately when ghes_edac is enabled. Similar
change can be made to other edac drivers as necessary.
Also,
The ghes_edac driver was introduced in 2013 [1], but it has not been
enabled by any distro yet. This is because the driver obtains error
info from firmware interfaces, which are not properly implemented on
many platforms.
To get out from this situation, add a platform check to selectively
enable
Only a single edac driver can be enabled for EDAC MC. When ghes_edac
is enabled, a regular edac driver for the CPU type / platform still
attempts to register itself and fails in edac_mc_add_mc().
Add edac_get_owner() so that regular edac drivers can check the owner
of EDAC MC without calling edac
Convert to use acpi_match_platform_list() for the platform check.
There is no change in functionality.
Signed-off-by: Toshi Kani
Acked-by: Srinivas Pandruvada
Reviewed-by: Borislav Petkov
Cc: "Rafael J. Wysocki"
Cc: Srinivas Pandruvada
Cc: Len Brown
Cc: Borislav Petkov
---
drivers/cpufreq/
ACPI OEM ID / OEM Table ID / Revision can be used to identify
a platform based on ACPI firmware info. acpi_blacklisted(),
intel_pstate_platform_pwr_mgmt_exists(), and some other funcs,
have been using similar check to detect a list of platforms
that require special handlings.
Move the platform ch
On 08/17, Thierry Reding wrote:
> On Thu, Jul 27, 2017 at 11:54:06AM -0700, Stephen Boyd wrote:
> > On 07/26, Peter De Schrijver wrote:
> > > On Tue, Jul 25, 2017 at 06:37:46PM -0700, Stephen Boyd wrote:
> > > > On 07/25, Peter De Schrijver wrote:
> > > > > A number of smaller fixes and simplificat
On 08/14, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> This patch adds missing LPASS smmu clks which are required by the audio
> driver.
>
> Signed-off-by: Srinivas Kandagatla
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora F
On 08/23, Stephen Boyd wrote:
> Silence the sparse warning
>
> clk/rockchip/clk.c:172:6: warning: symbol 'rockchip_fractional_approximation'
> was not declared. Should it be static?
>
> Cc: Elaine Zhang
> Cc: Heiko Stuebner
> Signed-off-by: Stephen Boyd
> ---
Applied to clk-next
--
Qualcom
On Wed, 23 Aug 2017, Roman Gushchin wrote:
> > It's better to have newbies consult the documentation once than making
> > everybody deal with long and cumbersome names for the rest of time.
> >
> > Like 'ls' being better than 'read_and_print_directory_contents'.
>
> I don't think it's a good arg
On Wed, Aug 23, 2017 at 06:54:52PM -0400, Tom Rini wrote:
> Ugh, typo on my part proving your point :) I meant _a_36afb... which is
> "ASoC: rt5677: Introduce proper table for ACPI enumeration". My gut
The code that's causing issues looks like it's generic ACPI code which
is worrying me, it loo
On Wed, 2017-08-23 at 18:12 +0200, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> Please use a more descriptive patch subject, i.e.
> "fbdev: vgastate: fix checkpatch.pl reported warnings".
>
> Please also cc: fbdev mailing list (linux-fb...@vger.kernel.org
> on fbdev patches).
>
> On Monday, August
On Wed, Aug 23, 2017 at 12:48:29PM -0400, Nick Fox wrote:
> Apologies for the spam, but I think my last reply got rejected by Google for
> some reason and didn't get delivered to the linux-kernel mailing list. My
> original reply is below:
You can not send html email to vger.kernel.org, it will be
On Wed, Aug 23, 2017 at 08:46:39AM -0700, Sherry Yang wrote:
> Use helper functions buffer_next and buffer_prev instead
> of list_entry to get the next and previous buffers.
>
> Signed-off-by: Sherry Yang
> ---
> drivers/android/binder_alloc.c | 24 +++-
> 1 file changed, 15
Hi Rob,
On 2017년 08월 24일 03:09, Rob Herring wrote:
> On Thu, Jul 20, 2017 at 12:25 AM, MyungJoo Ham
> wrote:
>>> On 2017년 07월 19일 06:42, Rob Herring wrote:
Now that we have a custom printf format specifier, convert users of
full_name to use %pOF instead. This is preparation to remove s
On Wed, Aug 23, 2017 at 08:44:46AM -0700, Randy Dunlap wrote:
> On 08/23/2017 06:22 AM, Arnd Bergmann wrote:
> > Like the version in drivers/net/wireless, this driver requires the
> > MAC80211 framework, otherwise we run into a link error:
> >
> > ERROR: "ieee80211_rx_irqsafe" [drivers/staging/rtl
On Wed, 23 Aug 2017, Roman Gushchin wrote:
> Traditionally, the OOM killer is operating on a process level.
> Under oom conditions, it finds a process with the highest oom score
> and kills it.
>
> This behavior doesn't suit well the system with many running
> containers:
>
> 1) There is no fair
On Wed, Aug 23, 2017 at 02:45:51PM +0530, Janani S wrote:
> This patch solves the following warning shown by the checkpatch script
> WARNING: Comparisons should place the constants on the right side of
> the test
>
> Signed-off-by: Janani Sankara Babu
Your "From:" line does not match this :(
On Wed, Aug 23, 2017 at 03:31:46PM +0800, Shurong Zhang wrote:
> Replace hard-coded function names in strings with "%s", __func__
> in the olpc_dcon.c file. Issue found by checkpatch.pl.
>
> Signed-off-by: Shurong Zhang
> ---
> drivers/staging/olpc_dcon/olpc_dcon.c | 2 +-
> 1 file changed, 1 i
Hi Catalin,
Today's linux-next merge of the arm64 tree got a conflict in:
arch/arm64/kernel/fpsimd.c
between commit:
096622104e14 ("arm64: fpsimd: Prevent registers leaking across exec")
from Linus' tree and commit:
cb84d11e1625 ("arm64: neon: Remove support for nested or hardirq kernel
On Wed, Aug 23, 2017 at 04:50:21PM +0530, Shubhrajyoti Datta wrote:
> Signed-off-by: Shubhrajyoti Datta
I can't take patches without any changelog text at all :(
The mm-of-the-moment snapshot 2017-08-23-16-26 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Wed, Aug 23, 2017 at 04:19:08PM -0700, Greg Kroah-Hartman wrote:
> On Wed, Aug 23, 2017 at 08:44:46AM -0700, Randy Dunlap wrote:
> > On 08/23/2017 06:22 AM, Arnd Bergmann wrote:
> > > Like the version in drivers/net/wireless, this driver requires the
> > > MAC80211 framework, otherwise we run in
On Wed, Aug 23, 2017 at 07:50:46PM +0530, Kishon Vijay Abraham I wrote:
> Greg,
>
> On Wednesday 23 August 2017 07:09 PM, Arnd Bergmann wrote:
> > Casting between an 'int' and a pointer causes a warning on
> > 64-bit architectures in compile-testing this driver:
> >
> > drivers/phy/ralink/phy-ral
On Wed, Aug 23, 2017 at 11:17 AM, Linus Torvalds
wrote:
> On Wed, Aug 23, 2017 at 8:58 AM, Tim Chen wrote:
>>
>> Will you still consider the original patch as a fail safe mechanism?
>
> I don't think we have much choice, although I would *really* want to
> get this root-caused rather than just pa
El Tue, Aug 01, 2017 at 04:30:14PM +0900 Sergey Senozhatsky ha dit:
> On (07/31/17 10:50), Matthias Kaehlcke wrote:
> > zs_stat_inc/dec/get() uses enum zs_stat_type for the stat type, however
> > some callers pass an enum fullness_group value. Change the type to int
> > to reflect the actual use o
Hi Andrew,
On Wed, 23 Aug 2017 16:27:27 -0700 a...@linux-foundation.org wrote:
>
> * mm-page_alloc-rip-out-zonelist_order_zone-fix.patch
That patch has an "Author:" line instead of a "From:" line ("git am" objects).
Otherwise looks good.
--
Cheers,
Stephen Rothwell
Do you need a personal/business L0AN, if yes contact Softlink Int'L for more
info
Hi John,
On Wed, 23 Aug 2017 12:21:43 -0700 John Johansen
wrote:
>
> In file included from security/apparmor/ipc.c:23:0:
> security/apparmor/include/sig_names.h:26:3: error: 'SIGSTKFLT' undeclared
> here (not in a function)
> [SIGSTKFLT] = 16, /* -, 16, - */
> ^
> security/apparm
Changes since v5 [1]:
* Compile fixes from a much improved coccinelle semantic patch (thanks
Julia!) that adds a 'flags' argument to all the ->mmap()
implementations in the kernel. (0day-kbuild-robot)
* Make the deprecated MAP_DENYWRITE and MAP_EXECUTABLE flags return
EOPNOTSUPP with the new
The mmap(2) syscall suffers from the ABI anti-pattern of not validating
unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a
mechanism to define new behavior that is known to fail on older kernels
without the support. Define a new mmap3 syscall that checks for
unsupported flags at
A common pattern for granting a privilege to an unprivileged process is
to pass it an established file descriptor over a unix domain socket.
This enables fine grained access to the MAP_DIRECT mechanism instead of
requiring the mapping process have CAP_LINUX_IMMUTABLE.
Cc: Jan Kara
Cc: Jeff Moyer
MAP_DIRECT is an mmap(2) flag with the following semantics:
MAP_DIRECT
When specified with MAP_SHARED a successful fault in this range
indicates that the kernel is maintaining the block map (user linear
address to file offset to physical address relationship) in a manner
that no external
We are running running short of vma->vm_flags. We can avoid needing a
new VM_* flag in some cases if the original @flags submitted to mmap(2)
is made available to the ->mmap() 'struct file_operations'
implementation. For example, the proposed addition of MAP_DIRECT can be
implemented without taking
When a filesystem sees this flag set it will not allow changes to the
file-offset to physical-block-offset relationship of any extent in the
file. The extent of the extents covered by the global S_IOMAP_SEALED is
filesystem specific. In other words it is similar to the inode-wide
XFS_DIFLAG2_REFLIN
Hello all,
This is the second try for fixing the regression in the BSG-interface that
exists since v4.11 (for more infos see the first series).
I separated my other changes from the bug-fix so that it is easier to apply
if judged good. I will rebase my cleanups I sent in v1 and send them when I
g
Since we split the scsi_request out of struct request bsg fails to
provide a reply-buffer for the drivers. This was done via the pointer
for sense-data, that is not preallocated anymore.
Failing to allocate/assign it results in illegal dereferences because
LLDs use this pointer unquestioned.
An e
On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wrote:
> On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote:
>
> > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote:
> > > Not all devices with ACPI and this combination of sound devices will
> > > have the required information provi
On Tue, Aug 15, 2017 at 12:21 AM, Andrew Jeffery wrote:
> In addition to the base, low and high clock configuration, the AC timing
> register #1 on the AST2400 houses fields controlling:
>
> 1. tBUF: Minimum delay between Stop and Start conditions
> 2. tHDSTA: Hold time for the Start condition
> 3
Hi
On 2017-08-16, Linus Torvalds wrote:
> On Wed, Aug 16, 2017 at 4:51 PM, Eric W. Biederman
> wrote:
[...]
> Maybe this attached patch is better anyway. It's smaller, because it
> keeps more closely to the old code, and just adds a mntput() in all
> the exit cases, and depends on the "path_get()
Arnd Bergmann, testing gcc-8, encountered the following:
> This is an interesting regression with gcc-8, showing a harmless
> warning for correct code:
>
>In file included from include/linux/kernel.h:13:0,
>...
>from drivers/scsi/lpfc/lpfc_debugfs.c:23:
>include/linux/printk.h:301:2: e
On (08/23/17 16:48), Petr Mladek wrote:
[..]
> Sometimes people seems unclear when to use the %pS or %pF printk format.
> For example, see commit 51d96dc2e2dc ("random: fix warning message on ia64
> and parisc") which fixed such a wrong format string.
>
> The documentation should be more clear abo
On Wed, Aug 23, 2017 at 5:24 PM, Stefan Lippers-Hollmann wrote:
>
> This patch[1] as part of 4.13-rc6 (up to, at least,
> v4.13-rc6-45-g6470812e2226) introduces a regression for me when using
> pbuilder 0.228.7[2] (a helper to build Debian packages in a chroot and
> to create and update its chroot
On 8/24/17 00:27, Martin K. Petersen wrote:
>
> Hi Bart,
>
>> Had you noticed that Damien had asked not to send the "sd_zbc: Write
>> unlock zone from sd_uninit_cmnd()" patch to Linus without my "scsi-mq:
>> Always unprepare before requeuing a request" patch?
>
> He did change his mind later in
On Tue, Aug 22, 2017 at 10:25:42AM +0100, Juri Lelli wrote:
> Hi,
>
> On 22/08/17 17:30, Byungchul Park wrote:
> > It would be better to try to check other siblings first if
> > SD_PREFER_SIBLING is flaged when pushing tasks - migration.
> >
> > Signed-off-by: Byungchul Park
> > Suggested-by: Pe
On Thu, Aug 24, 2017 at 01:47:08AM +0300, Alexey Khoroshilov wrote:
> There are no checks for dma mapping errors in pch_udc.
> Tha patch adds the checks and error handling code.
> Compile tested only.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Kho
As of_device_get_modalias() returns the number of bytes that would have
been written to the target string, regardless of how much did fit in the
buffer, it's possible that the returned index points beyond the buffer
passed to of_device_modalias() - causing memory beyond the buffer to be
null termin
of_device_request_module() calls of_device_get_modalias() with "len" 0,
to calculate the size of the buffer needed to store the result, but due
to integer promotion the ssize_t "len" will be compared as unsigned with
strlen(compat) and the loop will generally never break. This results in
a call to
Hello Steven,
Can I keep your reviewed-by with comments modified?
->8-
>From 285e72aff363f3f84a8ccf05c7236a0c849f8944 Mon Sep 17 00:00:00 2001
From: Byungchul Park
Date: Thu, 24 Aug 2017 09:59:10 +0900
Subject: [PATCH v10 2/2] sched/rt: Add support for SD_PREFER_SIBLING on
find_lowest_r
Change from v9
-. modify a comment a bit so to be more clear
Change from v8
-. add suggested-by Peterz
-. add several comments
Change from v7
-. fix a trivial typo
-. modify commit messages to explain what it does more clearly
-. simplify code with an existing macro
Change from
It would be better to try to check other siblings first if
SD_PREFER_SIBLING is flaged when pushing tasks - migration.
Suggested-by: Peter Zijlstra
Signed-off-by: Byungchul Park
Acked-by: Juri Lelli
---
kernel/sched/deadline.c | 80 -
1 file chan
>On 23.08.2017 08:06, Paul Mackerras wrote:
>> On Wed, Aug 23, 2017 at 01:43:08AM +, Nixiaoming wrote:
On 22.08.2017 17:15, David Hildenbrand wrote:
> On 22.08.2017 16:28, nixiaoming wrote:
>> miss kfree(stt) when anon_inode_getfd return fail so add check
>> anon_inode_getfd r
Boris,
Sorry for late reply. I missed this email earlier.
On 8/15/17 00:43, Borislav Petkov wrote:
diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
index 79895ae..2dd5b11 100644
--- a/kernel/sched/topology.c
+++ b/kernel/sched/topology.c
@@ -1335,6 +1335,10 @@ void sched_init_numa
Hi Peter,
On 8/14/17 14:44, Suravee Suthikulpanit wrote:
On 8/11/17 16:15, Peter Zijlstra wrote:
On Fri, Aug 11, 2017 at 12:58:22PM +0700, Suravee Suthikulpanit wrote:
On 8/11/17 11:57, Suravee Suthikulpanit wrote:
[...]
@@ -1445,9 +1448,24 @@ void sched_init_numa(void)
tl[i] =
On Wed, 23 Aug 2017, John Johansen wrote:
>
> In file included from security/apparmor/ipc.c:23:0:
> security/apparmor/include/sig_names.h:26:3: error: 'SIGSTKFLT' undeclared
> here (not in a function)
> [SIGSTKFLT] = 16, /* -, 16, - */
> ^
> security/apparmor/include/sig_names.h:2
On Wed, Aug 23, 2017 at 5:42 PM, Linus Torvalds
wrote:
>
> Let me try to think about alteratives. Clearly this is a regression
> and I need to fix it, I just need to figure out _how_.
Ok, sadly, I think it's unfixable with the current model.
We literally used to keep the wrong 'struct path' arou
Hi all,
As expetced, today's linux-next merge of the wireless-drivers-next tree
got a conflict in:
drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c
between commit:
92b0f7b26b31 ("iwlwifi: split the regulatory rules when the bandwidth flags
require it")
from Linus' tree and commit:
b8
On Wed, Aug 23, 2017 at 09:45:24AM +0200, Mickaël Salaün wrote:
> >>
> >> +union bpf_prog_subtype {
> >> + struct {
> >> + __u32 abi; /* minimal ABI version, cf. user doc */
> >
> > the concept of abi (version) sounds a bit weird to me.
> > Why bother with it at all?
> > Once
601 - 700 of 847 matches
Mail list logo
