On 07/24/2015 at 06:15 PM, Bjorn Helgaas wrote:
> [+cc Tejun, linux-ide]
>
> On Thu, Jul 23, 2015 at 11:22 PM, Andreas Hartmann
> wrote:
>> On Tue, Jul 21, 2015 at 06:35PM +0200, Joerg Roedel wrote:
>>> On Tue, Jul 21, 2015 at 06:20:23PM +0200, Andreas Hartmann wrote:
[ 48.193901] <6>[fglr
The debug_read_tlb() uses the sprintf() functions directly on the buffer
allocated by buf = kmalloc(count), without taking into account the size
of the buffer, with the consequence corrupting the heap, depending on
the count requested by the user.
The patch fixes the issue replacing sprintf() by s
On Tue, Jul 21, 2015 at 06:35PM +0200, Joerg Roedel wrote:
> On Tue, Jul 21, 2015 at 06:20:23PM +0200, Andreas Hartmann wrote:
>> [ 48.193901] <6>[fglrx] Firegl kernel thread PID: 1840
>> [ 48.193985] <6>[fglrx] Firegl kernel thread PID: 1841
>> [ 48.194063] <6>[fglrx] Firegl kernel thread PI
Am 21.07.2015 um 18:35 schrieb Joerg Roedel:
> On Tue, Jul 21, 2015 at 06:20:23PM +0200, Andreas Hartmann wrote:
>> [ 48.193901] <6>[fglrx] Firegl kernel thread PID: 1840
>> [ 48.193985] <6>[fglrx] Firegl kernel thread PID: 1841
>> [ 48.194063] <6>[fglrx] Firegl kernel thread PID: 1842
>> [
[ note: this patch is in a dev branch for test coverage, safe to
disregard for now ]
On Wed, Jul 22, 2015 at 4:32 PM, kernel test robot
wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.g
Hi Jörg,
I attached the dmesg output of the boot seuqence. This time after
reboot, the amount of IO_PAGE_FAULTs is not that much, but now, I got a
few ata3.00 errors.
Am 21.07.2015 um 17:56 schrieb Joerg Roedel:
> Hi Andreas,
>
> On Tue, Jul 21, 2015 at 09:34:46AM -0600, Alex Williamson wrote:
On 07/23/2015 09:52 AM, Mark Rutland wrote:
[...]
+MSI clients
+===
+
+MSI clients are devices which generate MSIs. For each MSI they wish to
+generate, the doorbell and payload may be configured, though sideband
+information may not be configurable.
+
+Required properties:
+-
This makes sure it won't be possible to accidentally leak format
strings into iommu device names. Current name allocations are safe,
but this makes the "%s" explicit.
Signed-off-by: Kees Cook
---
drivers/iommu/dmar.c| 2 +-
drivers/iommu/intel-iommu.c | 2 +-
2 files changed, 2 insertion
New information: During testing, I now realized that Linux 4.0.9 shows
the same problem ... . I'm now testing 3.19.4.
Regards,
Andreas
On 07/24/2015 at 06:15 PM, Bjorn Helgaas wrote:
> [+cc Tejun, linux-ide]
>
> On Thu, Jul 23, 2015 at 11:22 PM, Andreas Hartmann
> wrote:
>> On Tue, Jul 21, 20