Commit-ID: c818cc063089e78bc31845d1eb6a1f0bedee1eae
Gitweb: https://git.kernel.org/tip/c818cc063089e78bc31845d1eb6a1f0bedee1eae
Author: Jiri Olsa
AuthorDate: Mon, 2 Jul 2018 15:42:02 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 11 Jul 2018 09:43:03 -0400
perf stat: Fix
Commit-ID: db0ba84c04ef2cf293aaada5ae97531127844d9d
Gitweb: https://git.kernel.org/tip/db0ba84c04ef2cf293aaada5ae97531127844d9d
Author: Janne Huttunen
AuthorDate: Mon, 9 Jul 2018 13:59:50 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 11 Jul 2018 09:45:24 -0400
perf script
Commit-ID: 32aa928a7b817140c84987b726d5014911808fa4
Gitweb: https://git.kernel.org/tip/32aa928a7b817140c84987b726d5014911808fa4
Author: Jeremy Cline
AuthorDate: Tue, 10 Jul 2018 11:46:12 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 11 Jul 2018 09:48:31 -0400
perf tools:
On Thu, Jul 12, 2018 at 05:01:30PM +0900, Masahiro Yamada wrote:
>
> This series renames LDFLAGS to KBUILD_LDFLAGS
> after some Makefile cleanups.
>
> Currently, the last patch does not apply to Linus' tree
> due to missing pre-requisite patches.
>
> I will resolve conflicts as needed.
>
>
>
Use ssize_t for rets variables in mei_write(), mei_read(), and
mei_cl_write() as well as change the return type of mei_cl_write()
to ssize_t, to prevent assignment of possible 64bit size_t
to int 32 bit variable.
As by product also eliminate warning
drivers/misc/mei/client.c:1702:11: warning:
In for loops use same type for counter variable
as has the limiting variable.
drivers/misc/mei/bus-fixup.c:489:16: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
drivers/misc/mei/hw-txe.c:725:13: warning: comparison between signed and
unsigned integer
mei_hbuf_empty_slots() may return with an error in case
of circular buffer overflow. This type of error may
be caused only by a bug. However currently, the error
won't be detected due signed type promotion in comparison to u32.
We add explicit check for less then zero and explicit cast
in
Add more type conversion issues.
The first one in also address the type promotion bug,
as reported by Dan Carpenter. The particular error should
not really happen unless something is completely wrong, so no urge
to merging them into stable.
Tomas Winkler (3):
mei: check for error returned from
Hi Andy,
On Thu, Jul 12, 2018 at 12:03:08PM +0300, Andy Shevchenko wrote:
> On Wed, Jul 11, 2018 at 7:07 PM, Tycho Andersen wrote:
>
> > Anyway, since the lock is not acquired, if uart_shutdown() is called, the
> > last chunk of that function may release state->xmit.buf before its assigned
> >
On 12.07.2018 09:09, Thomas Richter wrote:
> With commit eca0fa28cd0d ("perf record: Provide detailed information on s390
> CPU")
> s390 platform provides detailed type/model/capacitiy information
> in the CPU indentifier string instead of just "IBM/S390".
>
> This breaks perf kvm support which
On Wed, Jul 11, 2018 at 8:47 PM Yixun Lan wrote:
>
> Hi Rob
>
> see my comments
>
> On 07/12/18 03:43, Rob Herring wrote:
> > On Tue, Jul 10, 2018 at 04:36:56PM +, Yixun Lan wrote:
> >> Document the MMC sub clock controller driver, the potential consumer
> >> of this driver is MMC or NAND.
>
Separating threads::last_match cache set into
separate threads__set_last_match function.
This will be useful in following patch.
Link: http://lkml.kernel.org/n/tip-r2phhluimtb4747rug66m...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/machine.c | 12 +---
1 file changed, 9
Separating threads::last_match cache read/check into
separate threads__get_last_match function. This will
be useful in following patch.
Link: http://lkml.kernel.org/n/tip-z4zzlpp3vusjued0gzp5u...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/machine.c | 39
hi,
perf top is occasionaly crashes on hitting assert, because of
the synthesize function that runs on multiple threads now.
I found some issues with list/tree accessing and this patchset
is trying to fix them.
I was runing 'perf top' in a loop with attached change below
and haven't hit any
We occasionaly hit following assert failure in perf top,
when processing the /proc info in multiple threads.
perf: ...include/linux/refcount.h:109: refcount_inc:
Assertion `!(!refcount_inc_not_zero(r))' failed.
The gdb backtrace looks like this:
[Switching to Thread 0x711ba700
There's an issue with using threads::last_match in multithread
mode which is enabled during the perf top synthesize. It might
crash with following assertion:
perf: ...include/linux/refcount.h:109: refcount_inc:
Assertion `!(!refcount_inc_not_zero(r))' failed.
The gdb backtrace looks
On Wed, Jul 11, 2018 at 02:04:49PM -0700, Andrew Morton wrote:
> On Wed, 11 Jul 2018 09:49:01 -0700 syzbot
> wrote:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:98be45067040 Add linux-next specific files for 20180711
> > git tree: linux-next
> >
On 07/06/2018 04:26 PM, Halil Pasic wrote:
On 06/29/2018 11:11 PM, Tony Krowiak wrote:
From: Tony Krowiak
Introduces a new structure for storing the AP matrix configured
for the mediated matrix device via its sysfs attributes files.
Signed-off-by: Tony Krowiak
---
On 07/12/2018 01:22 AM, Halil Pasic wrote:
On 06/29/2018 11:11 PM, Tony Krowiak wrote:
From: Tony Krowiak
Configures the AP adapters, usage domains and control domains for the
KVM guest from the matrix configured via the mediated matrix device's
sysfs attribute files.
[..]
+
+static void
On 07/12/2018 03:28 PM, Halil Pasic wrote:
On 06/29/2018 11:11 PM, Tony Krowiak wrote:
From: Tony Krowiak
Configures the AP adapters, usage domains and control domains for the
[..]
+static inline void kvm_ap_clear_crycb_masks(struct ap_matrix_mdev
*matrix_mdev)
+{
+
On Sun, 01 Jul 2018 21:22:46 +0900,
Mike Rapoport wrote:
>
> (added Yoshinori Sato, here's the beginning of the discussion:
> https://lore.kernel.org/lkml/20180625140754.gb29...@dhcp22.suse.cz/)
>
> On Wed, Jun 27, 2018 at 07:02:06PM +0300, Mike Rapoport wrote:
> > On Wed, Jun 27, 2018 at
Greg Kurz wrote on Thu, Jul 12, 2018:
> This is true when all tags have been used at least once. But the current code
> lazily allocates the wait_queue_head_t, ie, only when a tag is used for the
> first time. Your patch causes a full row of wait_quest_head_t to be
> pre-allocated.
>
> ie,
On 07/11/2018 09:29 AM, Juri Lelli wrote:
> Mark noticed that syzkaller is able to reliably trigger the following
>
> dl_rq->running_bw > dl_rq->this_bw
> WARNING: CPU: 1 PID: 153 at kernel/sched/deadline.c:124
> switched_from_dl+0x454/0x608
> Kernel panic - not syncing: panic_on_warn set
- Join split message for easier grepping,
- Use pr_*() instead of printk*(),
- Use %u to format unsigned cpu numbers.
Signed-off-by: Geert Uytterhoeven
---
kernel/time/hrtimer.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/kernel/time/hrtimer.c
On Thu, Jul 12, 2018 at 10:29 AM, Christoph Hellwig wrote:
> On Fri, Jul 06, 2018 at 10:42:47PM -0700, Deepa Dinamani wrote:
>
>> -#ifdef CONFIG_COMPAT
>> -
>> COMPAT_SYSCALL_DEFINE2(clock_adjtime, clockid_t, which_clock,
>> struct compat_timex __user *, utp)
>> {
>> @@
On Wed, Jul 11, 2018 at 4:14 PM, Dave Hansen wrote:
> On 07/11/2018 04:07 PM, Andy Lutomirski wrote:
>> Could the cause be an overflow of the IRQ stack? I’ve been meaning
>> to put guard pages on all the special stacks for a while. Let me see
>> if I can do that in the next couple days.
>
> But
On Wed, 11 Jul 2018 09:00:07 -0400
Brian Masney wrote:
> On Wed, Jul 11, 2018 at 12:29:33PM +, Jean-Baptiste Maneyrol wrote:
> > Hello,
> >
> > I really don't like the idea to have regulator handled inside the
> > driver. I know this was done like that before for Nexus 5, but I
> > think
On Tue, 10 Jul 2018 21:09:30 -0400
Brian Masney wrote:
> This patch adds support for the MPU 6515 variant. Confirmed that the
> driver functions correctly on a LG Nexus 5 (hammerhead) phone.
>
> Signed-off-by: Brian Masney
> Signed-off-by: Jonathan Marek
> ---
> This is a variation of
Currently PCI_BRIDGE_CTL_SERR is being enabled only in
ACPI flow.
This bit is required for forwarding errors reported
by EP devices to upstream device.
This patch enables SERR# for Type-1 PCI device.
Signed-off-by: Bharat Kumar Gogada
---
drivers/pci/pcie/aer.c | 23 +++
1
On Wed, 11 Jul 2018 14:02:23 -0700
Matthew Wilcox wrote:
> On a 64-bit system, the wait_queue_head_t is 24 bytes while the pointer
> to it is 8 bytes. Growing the p9_req_t by 16 bytes is better than
> performing a 24-byte memory allocation.
>
This is true when all tags have been used at least
Andy Lutomirski wrote:
> > On Jul 11, 2018, at 12:22 AM, David Howells wrote:
> >
> > Andy Lutomirski wrote:
> >
> >>> sfd = fsopen("ext4", FSOPEN_CLOEXEC);
> >>> write(sfd, "s /dev/sdb1"); // note I'm ignoring write's length arg
> >>
> >> Imagine some malicious program passes sfd as
We now have all VMAs with ->vm_ops set and don't need to check it for
NULL everywhere.
Signed-off-by: Kirill A. Shutemov
---
fs/binfmt_elf.c | 2 +-
fs/kernfs/file.c | 20 +---
fs/proc/task_mmu.c | 2 +-
kernel/events/core.c | 2 +-
kernel/fork.c| 2 +-
vma_is_anonymous() relies on ->vm_ops being NULL to detect anonymous
VMA. This is unreliable as ->mmap may not set ->vm_ops.
False-positive vma_is_anonymous() may lead to crashes:
next 8801ce5e7040 prev 8801d20eca50 mm 88019c1e13c0
prot 27 anon_vma 88019680cdd8
Fix crash found by syzkaller.
The fix allows to remove ->vm_ops checks.
v2:
- Catch few more cases where we need to initialize ->vm_ops:
+ nommu;
+ ia64;
- Make sure that we initialize ->vm_ops even if ->mmap failed.
We need ->vm_ops in error path too.
Kirill A. Shutemov (2):
mm:
2018-07-12 20:08 GMT+09:00 Uwe Kleine-König :
> On Thu, Jul 12, 2018 at 07:38:36PM +0900, Masahiro Yamada wrote:
>> Suppress warnings for systems that do not recognize LFS_*.
>>
>> getconf: no such configuration parameter `LFS_CFLAGS'
>> getconf: no such configuration parameter `LFS_LDFLAGS'
>>
On Wed, Jul 11, 2018 at 03:16:36PM +0200, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> Add the ISO7816 ioctl and associated accessors and data structure.
> Drivers can then use this common implementation to handle ISO7816.
>
> Signed-off-by: Nicolas Ferre
>
On Wed, Jul 11, 2018 at 03:26:23PM +0200, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> In atmel_shutdown() we call atmel_stop_rx() and atmel_stop_tx() functions.
> Prevent the rx restart that is implemented in RS485 or ISO7816 modes when
> calling atmel_stop_tx() by using the atomic
On Wed, Jul 11, 2018 at 03:16:38PM +0200, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> In atmel_shutdown() we call atmel_stop_rx() and atmel_stop_tx() functions.
> Prevent the rx restart that is implemented in RS485 or ISO7816 modes when
> calling atmel_stop_tx() by using the atomic
On Wed, Jul 11, 2018 at 03:16:37PM +0200, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> When mode is set in atmel_config_iso7816() we backup last RS232 mode
> for coming back to this mode if requested.
> Also allow setup of T=0 and T=1 parameter and basic support in set_termios
> function
On Wed, Jul 11, 2018 at 03:16:36PM +0200, Ludovic Desroches wrote:
> From: Nicolas Ferre
>
> Add the ISO7816 ioctl and associated accessors and data structure.
> Drivers can then use this common implementation to handle ISO7816.
>
> Signed-off-by: Nicolas Ferre
>
On 12/07/2018 4:55 PM, Jesper Dangaard Brouer wrote:
On Thu, 12 Jul 2018 14:54:08 +0200
Michal Hocko wrote:
[CC Jesper - I remember he was really concerned about the worst case
latencies for highspeed network workloads.]
Cc. Tariq as he have hit some networking benchmarks (around
2018-07-12 3:36 GMT+09:00 Constantine Shulyupin :
> Signed-off-by: Constantine Shulyupin
> ---
Applied to linux-kbuild/fixes. Thanks!
> scripts/tags.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index
On Wed, Jul 11, 2018 at 10:07:44AM -0600, Tycho Andersen wrote:
> + if (uport)
> + spin_lock_irqsave(>lock, flags);
That's the same thing as just calling uart_port_lock(), why aren't you
doing that?
thanks,
greg k-h
On Thu, Jul 12, 2018 at 5:43 AM Al Viro wrote:
>
> A question regarding the customs in such situations - are previous
> Reviewed-by/Acked-by normally kept across rebases like that?
Yeah, unless there were big changes, keep the reviewed/acked-by lines.
Otherwise you'd never be able to handle
On Wed, Jul 11, 2018 at 02:00:56PM -0600, Tycho Andersen wrote:
> On Wed, Jul 11, 2018 at 02:49:08PM -0500, Serge E. Hallyn wrote:
> > Quoting Tycho Andersen (ty...@tycho.ws):
> > > We have reports of the following crash:
> > >
> > > PID: 7 TASK: 88085c6d61c0 CPU: 1 COMMAND:
On Thu, Jul 12, 2018 at 05:56:24PM +0300, Kirill A. Shutemov wrote:
>
> Fix crash found by syzkaller.
>
> The fix allows to remove ->vm_ops checks.
>
> v2:
> - Catch few more cases where we need to initialize ->vm_ops:
>+ nommu;
>+ ia64;
> - Make sure that we initialize ->vm_ops even
On Thu, Jul 12, 2018 at 05:04:38PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jul 11, 2018 at 10:07:44AM -0600, Tycho Andersen wrote:
> > + if (uport)
> > + spin_lock_irqsave(>lock, flags);
>
> That's the same thing as just calling uart_port_lock(), why aren't you
> doing that?
On Wed, Jul 11, 2018 at 6:54 PM Andrew Jeffery wrote:
>
> Hi Rob,
>
> Thanks for the response.
>
> On Thu, 12 Jul 2018, at 05:34, Rob Herring wrote:
> > On Wed, Jul 11, 2018 at 03:01:19PM +0930, Andrew Jeffery wrote:
> > > Baseboard Management Controllers (BMCs) are embedded SoCs that exist to
>
On Thu, 12 Jul 2018 16:40:12 +0200
Dominique Martinet wrote:
> Greg Kurz wrote on Thu, Jul 12, 2018:
> > This is true when all tags have been used at least once. But the current
> > code
> > lazily allocates the wait_queue_head_t, ie, only when a tag is used for the
> > first time. Your patch
Hi Marco,
On Thu, Jul 12, 2018 at 8:02 AM, Marco Felsch wrote:
> Add enable/disable support for switch regulators on pfuze100.
>
> Based on commit 5fe156f1cab4 ("regulator: pfuze100: add enable/disable for
> switch") which is reverted due to boot regressions by commit 464a5686e6c9
> ("regulator:
On Thu, Jul 12, 2018 at 8:02 AM, Marco Felsch wrote:
> +Optional properties:
> +- pfuze-disable-sw: Disable all unused switch regulators to save power
> + consumption. Attention, some platforms are using the switch regulators as
> DDR
> + ref or supply voltage. Mark these regulators as
On Thu, Jul 12, 2018 at 2:14 AM Frieder Schrempf
wrote:
>
> Hi Rob,
>
> On 11.07.2018 18:05, Rob Herring wrote:
> > On Thu, Jul 05, 2018 at 01:15:01PM +0200, Frieder Schrempf wrote:
> >> Adjust the documentation of the new SPI memory interface based
> >> driver to reflect the new drivers
On Wed, 27 Jun 2018 12:00:41 +0200
Pierre Morel wrote:
Apologies for the late answer, this topic had dropped off my radar.
> On 26/06/2018 18:00, Cornelia Huck wrote:
> > On Tue, 26 Jun 2018 13:04:12 +0200
> > Pierre Morel wrote:
> >
> >> On 19/06/2018 16:00, Cornelia Huck wrote:
> >>> On
On Thu, Jul 12, 2018 at 04:58:27PM +0200, Greg KH wrote:
> On Wed, Jul 11, 2018 at 03:26:23PM +0200, Ludovic Desroches wrote:
> > From: Nicolas Ferre
> >
> > In atmel_shutdown() we call atmel_stop_rx() and atmel_stop_tx() functions.
> > Prevent the rx restart that is implemented in RS485 or
2018-07-10 23:50 GMT+09:00 Paul Menzel :
> Date: Tue, 5 Jun 2018 19:00:22 +0200
>
> In 2016 GNU Make made a backwards incompatible change to the way '#'
> characters were handled in Makefiles when used inside functions or
> macros:
>
>
On Thu, Jul 12, 2018 at 01:02:39PM +0200, Marco Felsch wrote:
> +Optional properties:
> +- pfuze-disable-sw: Disable all unused switch regulators to save power
> + consumption. Attention, some platforms are using the switch regulators as
> DDR
> + ref or supply voltage. Mark these regulators
From: Bjorn Helgaas
halmac_pcie_reg.h is empty, so remove it and the only include of it.
Signed-off-by: Bjorn Helgaas
---
drivers/staging/rtlwifi/halmac/halmac_api.h |1 -
drivers/staging/rtlwifi/halmac/halmac_pcie_reg.h | 17 -
2 files changed, 18 deletions(-)
Add the device tree binding documentation for the ADXL372 3-axis digital
accelerometer.
Signed-off-by: Stefan Popa
---
Documentation/devicetree/bindings/iio/accel/adxl372.txt | 16
MAINTAINERS | 1 +
2 files changed, 17 insertions(+)
This patch adds the option for the user to select the sampling frequency.
Also, the user can read the available frequencies and read the currently
set frequency via the read_raw function. The frequency can be set via the
write_raw function.
When the frequency is set, the bandwidth is also checked
This patch adds the option for the user to select the filter bandwidth. The
user can also read the available bandwidths which are always adjusted to be
at most half of the sampling frequency. Furthermore, the currently selected
bandwidth can be read via the read_raw function, while the write_raw
This patch adds support for the adxl372 FIFO. In order to accomplish this,
triggered buffers were used.
The number of FIFO samples which trigger the watermark interrupt can be
configured by using the buffer watermark, while the format depends on the
selected channels.The FIFO data along with the
This patch adds basic support for Analog Devices ADXL372 SPI-Bus
Three-Axis Digital Accelerometer.
The device is probed and configured the with some initial default
values. With this basic driver, it is possible to read raw acceleration
data.
Datasheet:
On Thu, Jul 12, 2018 at 09:08:22AM -0600, Tycho Andersen wrote:
> On Thu, Jul 12, 2018 at 05:04:38PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Jul 11, 2018 at 10:07:44AM -0600, Tycho Andersen wrote:
> > > + if (uport)
> > > + spin_lock_irqsave(>lock, flags);
> >
> > That's the same
On Thu, 12 Jul 2018 17:26:00 +0200,
Pierre-Louis Bossart wrote:
>
> On 7/11/18 3:43 AM, Srinivas Kandagatla wrote:
> > This patch aims at add achieving dynamic behaviour of audio card when
> > the dependent components disappear and reappear.
> >
> > With this patch the card is removed if any of
2018-07-10 16:38 GMT+09:00 Jiri Olsa :
> On Mon, Jul 09, 2018 at 05:45:56PM -0700, Laura Abbott wrote:
>> Commit 0c3b7e42616f ("tools build: Add support for host programs format")
>> introduced host_c_flags which referenced CHOSTFLAGS. The actual name of the
>> variable is HOSTCFLAGS. Fix this up.
2018-07-10 16:38 GMT+09:00 Jiri Olsa :
> On Mon, Jul 09, 2018 at 05:45:57PM -0700, Laura Abbott wrote:
>> The final link of fixdep uses LDFLAGS but not the existing HOSTLDFLAGS.
>> Fix this.
>>
>> Signed-off-by: Laura Abbott
>
> Acked-by: Jiri Olsa
>
Applied to linux-kbuild/fixes. Thanks!
>
Hello,
syzbot found the following crash on:
HEAD commit:c25c74b7476e Merge tag 'trace-v4.18-rc3-2' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=177bcec240
kernel config: https://syzkaller.appspot.com/x/.config?x=25856fac4e580aa7
On Thu, Jul 12, 2018 at 7:54 AM David Howells wrote:
>
> I think we *have* to open the source files/devices with the creds of whoever
> called fsopen() or fspick() - that way you can't upgrade your privs by passing
> your context fd to a suid program. To enforce this, I think it's simplest for
>
65ebcc115889 ("ARM: sti: Add STiH415 SOC support")
---
Problem was found by an experimental coccinelle script
Patch was compile tested with: multi_v7_defconfig (implies
CONFIG_ARCH_STI=y, CONFIG_SMP=y)
Patch is against 4.18-rc3 (localversion-next is next-20180712)
arch/arm/mach-sti/platsmp.
On Thu, Jul 12, 2018 at 08:05:26AM -0700, Linus Torvalds wrote:
> On Thu, Jul 12, 2018 at 5:43 AM Al Viro wrote:
> >
> > A question regarding the customs in such situations - are previous
> > Reviewed-by/Acked-by normally kept across rebases like that?
>
> Yeah, unless there were big changes,
On 7/12/18 10:42 AM, Takashi Iwai wrote:
On Thu, 12 Jul 2018 17:26:00 +0200,
Pierre-Louis Bossart wrote:
On 7/11/18 3:43 AM, Srinivas Kandagatla wrote:
This patch aims at add achieving dynamic behaviour of audio card when
the dependent components disappear and reappear.
With this patch the
On Thu, Jul 12, 2018 at 05:42:30PM +0200, Takashi Iwai wrote:
> Pierre-Louis Bossart wrote:
> > On 7/11/18 3:43 AM, Srinivas Kandagatla wrote:
> > > This patch aims at add achieving dynamic behaviour of audio card when
> > > the dependent components disappear and reappear.
> > Humm, no real
On Sun, Jul 01, 2018 at 07:45:08PM +0200, Lukas Wunner wrote:
> On Fri, Jun 29, 2018 at 03:27:39PM -0500, Bjorn Helgaas wrote:
> > --- /dev/null
> > +++ b/Documentation/PCI/submitting-patches.txt
> > @@ -0,0 +1,153 @@
> > +Start with Documentation/process/submitting-patches.rst for general
> >
On Thu, Jul 12, 2018 at 08:50:46AM -0700, Linus Torvalds wrote:
> But "write()" simply is *NOT* a good "command" interface. If you want
> to send a command, use an ioctl or a system call.
>
> Because it's not just about credentials. It's not just about fooling a
> suid app into writing an error
Hi Thomas,
On Thu, Jul 12, 2018 at 03:42:55PM +0200, Thomas Bogendoerfer wrote:
> Commit 205e1b7f51e4 ("dma-mapping: warn when there is no coherent_dma_mask")
> introduced a warning, if a device is missing a coherent_dma_mask.
> ESP and sonic are using dma mapping functions, so they need dma
On 07/12/2018 02:47 PM, Halil Pasic wrote:
On 06/29/2018 11:11 PM, Tony Krowiak wrote:
Implements the open callback on the mediated matrix device.
The function registers a group notifier to receive notification
of the VFIO_GROUP_NOTIFY_SET_KVM event. When notified,
the vfio_ap device driver
On 07/12/2018 06:51 AM, Guo Ren wrote:
On Wed, Jul 11, 2018 at 10:51:33AM +0100, David Howells wrote:
Can you say what the --target tuple should be so that I can add the arch to my
collection of Fedora cross-binutils and cross-gcc tools built from upstream
binutils and gcc sources?
Metor
On Thu, Jul 12, 2018 at 9:00 AM Al Viro wrote:
>
> Wait a sec - that's only a problem if your command contains pointer-chasing
> et.al.
No.
It's a problem if anybody ever does something like "let's have a
helper splice thread that uses splice to move data automatically from
one buffer to
On Thu, Jul 12, 2018 at 05:53:51AM -0700, Paul E. McKenney wrote:
> On Thu, Jul 12, 2018 at 01:00:42PM +0100, David Woodhouse wrote:
> >
> >
> > On Wed, 2018-07-11 at 14:08 -0700, Paul E. McKenney wrote:
> > >
> > > > Also... why in $DEITY's name was the existing
> > > >
Use strlcpy instead of strncpy to avoid gcc 8 warning:
warning: '__builtin_strncpy' specified bound 16 equals destination size
[-Wstringop-truncation]
The maximum length of the source string including terminating null is 5.
Hence it always fits in the destination buffer of length 16.
On Thu, Jul 12, 2018 at 10:54:05AM -0500, Pierre-Louis Bossart wrote:
> On 7/12/18 10:42 AM, Takashi Iwai wrote:
> > It's basically similar as the hotplug like USB, so I thought it would
> > work as is.
> Such transitions would probably not break userspace but they result from an
> explicit user
On Thu, Jul 12, 2018 at 03:48:21PM +0200, Peter Zijlstra wrote:
[ . . . ]
> I'm still hoping we can convince the PowerPC people that they're wrong,
> and get rid of this wart and just call all locks RCsc.
As always, I must defer to the PowerPC maintainers on this point.
Kirill, I am not trying to review this change (but it looks good to me),
just a silly question...
On 07/12, Kirill A. Shutemov wrote:
>
> This can be fixed by assigning anonymous VMAs own vm_ops and not relying
> on it being NULL.
I agree, this makes sense, but...
> If ->mmap() failed to set
> On Jul 12, 2018, at 7:54 AM, David Howells wrote:
>
> Andy Lutomirski wrote:
>
>>> On Jul 11, 2018, at 12:22 AM, David Howells wrote:
>>>
>>> Andy Lutomirski wrote:
>>>
> sfd = fsopen("ext4", FSOPEN_CLOEXEC);
> write(sfd, "s /dev/sdb1"); // note I'm ignoring write's length
This looks similar to my "[PATCH] kvm: nVMX: Restore exit qual for
VM-entry failure due to MSR loading"
On Thu, Jul 12, 2018 at 4:35 AM, Vitaly Kuznetsov wrote:
> Commit e79f245ddec1 ("X86/KVM: Properly update 'tsc_offset' to represent
> the running guest") introduced a regression in
On Fri, Jul 6, 2018 at 11:45 PM, Miklos Szeredi wrote:
> iput() ends up calling ->evict() on new inode, which is not yet initialized
> by owning fs. So use destroy_inode() instead.
>
> Add to sb->s_inodes list only if inode is not in I_CREATING state (meaning
> that it wasn't allocated with
Date: Sun, 8 Jul 2018 09:11:34 +0200
Defining `ATA_DEBUG` nothing can be really seen, as the log is spammed
with CDB messages.
Therefore, guard the print by `ATA_VERBOSE_DEBUG`.
Signed-off-by: Paul Menzel
---
drivers/ata/libata-scsi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
On Tue, Jul 10, 2018 at 1:38 PM Lina Iyer wrote:
>
> On Tue, Jul 10 2018 at 12:53 -0600, Evan Green wrote:
> >On Mon, Jul 9, 2018 at 10:27 AM Bjorn Andersson
> > wrote:
> >>
> >> Sorry for not getting back to you in a timely manner Evan, I wanted to
> >> read up more on the details of how this is
Date: Sun, 8 Jul 2018 09:18:21 +0200
Defining `ATA_DEBUG` there are a lof of messages like below in the log.
[ 16.345472] ata_sg_setup: 1 sg elements mapped
As that is too verbose, only output these messages in verbose debug.
Signed-off-by: Paul Menzel
---
drivers/ata/libata-core.c | 2
On Thu, Jul 12, 2018 at 09:07:36AM -0700, Linus Torvalds wrote:
> On Thu, Jul 12, 2018 at 9:00 AM Al Viro wrote:
> >
> > Wait a sec - that's only a problem if your command contains pointer-chasing
> > et.al.
>
> No.
>
> It's a problem if anybody ever does something like "let's have a
> helper
On Thu, Jul 12, 2018 at 9:23 AM Andy Lutomirski wrote:
>
> (Al- can’t we just stop allowing splice() at all on things that don’t use
> iov_iter?)
We could add a FMODE_SPLICE_READ/WRITE bit, and let people opt in to
splice. We probably should have.
But again, that really doesn't change the
On 07/12/2018 07:56 AM, Mark Rutland wrote:
> On Mon, Jul 09, 2018 at 06:42:29PM -0400, Boris Ostrovsky wrote:
>> On 07/02/2018 12:02 PM, Mark Rutland wrote:
>>> On Mon, Jul 02, 2018 at 05:46:55PM +0200, Peter Zijlstra wrote:
On Mon, Jul 02, 2018 at 04:12:50PM +0100, Mark Rutland wrote:
>
Adrian Reber writes:
> The CHECKPOINT_RESTORE configuration option was introduced in 2012 and
> combined with EXPERT. CHECKPOINT_RESTORE is already enabled in many
> distribution kernels and also part of the defconfigs of various
> architectures.
>
> To make it easier for distributions to
Hi Jiri,
On Thu, Jul 12, 2018 at 6:52 AM Jiri Olsa wrote:
>
> Stephan reported, that pipe mode does not carry the group
> information and thus the piped report won't display the
> grouped output for following command:
>
Thanks for fixing this quickly.
I think we should have more testing on the
On Thu, Jul 12, 2018 at 06:20:39PM +0200, Oleg Nesterov wrote:
> Kirill, I am not trying to review this change (but it looks good to me),
> just a silly question...
>
> On 07/12, Kirill A. Shutemov wrote:
> >
> > This can be fixed by assigning anonymous VMAs own vm_ops and not relying
> > on it
On Thu, Jul 12, 2018 at 9:31 AM Al Viro wrote:
>
> And seriously, ioctl? _That_ has a great track record...
I agree that a system call is likely saner. Especially since we'd have
one to _start_ this (ie "fsopen()") it would make sense to have the
one to finalize it.
> [1] one man's data is
On Thu, Jul 12, 2018 at 09:23:22AM -0700, Andy Lutomirski wrote:
> If you make a syscall that attaches a block device to an fscontext, you don’t
> need any of this. Heck, someone might actually *want* to grab a block device
> from a different namespace.
Fuck, NO. The whole notion of "block
On 12-07-18, 10:26, Pierre-Louis Bossart wrote:
> On 7/11/18 3:43 AM, Srinivas Kandagatla wrote:
> > This patch aims at add achieving dynamic behaviour of audio card when
> > the dependent components disappear and reappear.
> >
> > With this patch the card is removed if any of the dependent
On 07/11/2018 03:26 AM, jiangyiwen wrote:
> On 2018/7/10 6:29, Tomas Bortoli wrote:
>> The p9_client_version() does not initialize the version
>> pointer. If the call to p9pdu_readf() returns an error and version has not
>> been allocated in p9pdu_readf(), then the program will jump to the "error"
Hi,
Only one unusual about this pull-request - it is based on v4.18-rc2
because at v4.18-rc1 the NFS root boot, which I use at my testing
setup (https://krzk.eu), was broken.
Best regards,
Krzysztof
901 - 1000 of 1294 matches
Mail list logo
