On 14/08/2020 14:07, John Garry wrote:
BTW, as for the DMA/sg scatterlist code, it so happens in this case that
we try the dma alloc for size=0 in nvme_alloc_queue() - I know an
allocation for size=0 makes no sense, but couldn't we bit a bit more
robust?
it's giving ZERO_SIZE_PTR, which we
On 14/08/2020 13:08, Christoph Hellwig wrote:
[148.455065]__sg_alloc_table_from_pages+0xec/0x238
[148.459931]sg_alloc_table_from_pages+0x18/0x28
[148.464541]iommu_dma_alloc+0x474/0x678
[148.468455]dma_alloc_attrs+0xd8/0xf0
[148.472193]nvme_alloc_queue+0x114/0x160 [nvme]
[148.476798]nvme_reset_wor
On Fri, Aug 14, 2020 at 01:00:30PM +0100, John Garry wrote:
>
> > > I have experienced this this crash below on linux-next for the last few
> > > days
> > > on my arm64 system. Linus' master branch today also has it.
> > Adding Robin and the iommu list as this seems to be in the dma-iommu
> > cod
I have experienced this this crash below on linux-next for the last few days
on my arm64 system. Linus' master branch today also has it.
Adding Robin and the iommu list as this seems to be in the dma-iommu
code.
root@ubuntu:/home/john# insmod nvme.ko
[148.254564] nvme :81:00.0: Adding to
Hi Kieran,
On Thu, Aug 13, 2020 at 08:01:01PM +0100, Kieran Bingham wrote:
> Hi Randy,
>
> On 13/08/2020 19:35, Randy Dunlap wrote:
> > On 8/12/20 11:58 PM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> News: The merge window has opened, so please do not add any v5.10
> >> related material to yo
Hi Randy,
On 13/08/2020 19:35, Randy Dunlap wrote:
> On 8/12/20 11:58 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: The merge window has opened, so please do not add any v5.10
>> related material to your linux-next included branches until after the
>> merge window closes again.
>>
>> Changes
On 8/12/20 11:58 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: The merge window has opened, so please do not add any v5.10
> related material to your linux-next included branches until after the
> merge window closes again.
>
> Changes since 20200812:
>
on x86_64:
# CONFIG_GPIOLIB is not set
On Thu, Aug 13, 2020 at 12:00:19PM +0100, John Garry wrote:
> On 13/08/2020 07:58, Stephen Rothwell wrote:
> > Hi all,
>
> Hi guys,
>
> I have experienced this this crash below on linux-next for the last few days
> on my arm64 system. Linus' master branch today also has it.
Adding Robin and the
On 13/08/2020 07:58, Stephen Rothwell wrote:
Hi all,
Hi guys,
I have experienced this this crash below on linux-next for the last few
days on my arm64 system. Linus' master branch today also has it.
root@ubuntu:/home/john# insmod nvme.ko
[148.254564] nvme :81:00.0: Adding to iommu group
Hi all,
News: The merge window has opened, so please do not add any v5.10
related material to your linux-next included branches until after the
merge window closes again.
Changes since 20200812:
My fixes tree contains:
73c7adb54169 ("device_cgroup: Fix RCU list debugging warning")
Linus' tre
Hi all,
On Wed, 14 Aug 2019 08:14:18 +0200 Marek Szyprowski
wrote:
>
> On 2019-08-13 16:56, Steven Rostedt wrote:
> > This looks related to what Marek posted.
> >
> >
> > https://lore.kernel.org/linux-security-module/3028ed35-3b6d-459f-f3c8-103c5636f...@samsung.com/
> >
> > Care to apply the
Hi Steven,
On 2019-08-13 16:56, Steven Rostedt wrote:
> This looks related to what Marek posted.
>
>
> https://lore.kernel.org/linux-security-module/3028ed35-3b6d-459f-f3c8-103c5636f...@samsung.com/
>
> Care to apply the change he suggested to see if it fixes the issue for
> you. If it does, M
On Tue, Aug 13, 2019 at 10:56:45AM -0400, Steven Rostedt wrote:
>
> This looks related to what Marek posted.
>
>
> https://lore.kernel.org/linux-security-module/3028ed35-3b6d-459f-f3c8-103c5636f...@samsung.com/
>
> Care to apply the change he suggested to see if it fixes the issue for
> you.
On Tue, Aug 13, 2019 at 02:41:55PM +0200, Vasily Gorbik wrote:
> On Tue, Aug 13, 2019 at 07:19:24PM +1000, Stephen Rothwell wrote:
> > Merging security/next-testing (a4848e06f9af Merge branch 'next-lockdown'
> > into next-testing)
> > CONFLICT (content): Merge conflict in kernel/trace/trace_kprobe
This looks related to what Marek posted.
https://lore.kernel.org/linux-security-module/3028ed35-3b6d-459f-f3c8-103c5636f...@samsung.com/
Care to apply the change he suggested to see if it fixes the issue for
you. If it does, Marek, can you make an official patch?
-- Steve
On Tue, 13 Aug 2
On Tue, Aug 13, 2019 at 07:19:24PM +1000, Stephen Rothwell wrote:
> Merging security/next-testing (a4848e06f9af Merge branch 'next-lockdown' into
> next-testing)
> CONFLICT (content): Merge conflict in kernel/trace/trace_kprobe.c
> CONFLICT (content): Merge conflict in fs/tracefs/inode.c
> Applyin
Hi all,
Changes since 20190812:
New tree: spdx
The risc-v tree gained a conflict against the arm64 tree.
The crypto tree still had its build failure for which I disabled a driver
feature.
The amdgpu tree gained a build failure for which I applied a patch.
The sound-asoc tree still had its bui
On Mon, Aug 13, 2018 at 07:32:01PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180810:
>
> The ida tree lost its build failure.
>
> The akpm-current tree gained conflicts against the block tree and a
> build failure due to an interaction with the userns tree for which I
> applie
Hi all,
Changes since 20180810:
The ida tree lost its build failure.
The akpm-current tree gained conflicts against the block tree and a
build failure due to an interaction with the userns tree for which I
applied a merge fix patch.
Non-merge commits (relative to Linus' tree): 11957
10727 file
Hi all,
Changes since 20150812:
The v4l-dvb tree still had its build failure so I used the version from
next-20150810.
The bluetooth tree lost its build failure.
The staging tree gained a conflict against the tip tree.
The clk tree lost its build failure but gained a conflict against the
drm-m
Hi all,
Please do not add code intended for v3.18 until after v3.17-rc1 is
released.
Changes since 20140812:
*crickets*
Non-merge commits (relative to Linus' tree): 1630
1296 files changed, 35584 insertions(+), 16939 deletions(-)
---
On Tue, Aug 13, 2013 at 10:33 PM, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 10:25 PM, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 10:20 PM, Chris Wilson
>> wrote:
>>> On Tue, Aug 13, 2013 at 10:16:10PM +0200, Sedat Dilek wrote:
On Tue, Aug 13, 2013 at 10:10 PM, Chris Wilson
wro
On Tue, Aug 13, 2013 at 09:05:41PM +0200, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 8:53 PM, Chris Wilson
> wrote:
> > On Tue, Aug 13, 2013 at 08:40:37PM +0200, Sedat Dilek wrote:
> >> On Tue, Aug 13, 2013 at 8:01 PM, Chris Wilson
> >> wrote:
> >> > On Tue, Aug 13, 2013 at 07:53:25PM +0200,
On Tue, Aug 13, 2013 at 10:16:10PM +0200, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 10:10 PM, Chris Wilson
> wrote:
> > On Tue, Aug 13, 2013 at 09:05:41PM +0200, Sedat Dilek wrote:
> >> On Tue, Aug 13, 2013 at 8:53 PM, Chris Wilson
> >> wrote:
> >> > On Tue, Aug 13, 2013 at 08:40:37PM +0200,
On Tue, Aug 13, 2013 at 10:10 PM, Chris Wilson wrote:
> On Tue, Aug 13, 2013 at 09:05:41PM +0200, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 8:53 PM, Chris Wilson
>> wrote:
>> > On Tue, Aug 13, 2013 at 08:40:37PM +0200, Sedat Dilek wrote:
>> >> On Tue, Aug 13, 2013 at 8:01 PM, Chris Wilson
On Tue, Aug 13, 2013 at 8:53 PM, Chris Wilson wrote:
> On Tue, Aug 13, 2013 at 08:40:37PM +0200, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 8:01 PM, Chris Wilson
>> wrote:
>> > On Tue, Aug 13, 2013 at 07:53:25PM +0200, Sedat Dilek wrote:
>> >> Files attached.
>> >
>> > Can you also please att
On Tue, Aug 13, 2013 at 08:40:37PM +0200, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 8:01 PM, Chris Wilson
> wrote:
> > On Tue, Aug 13, 2013 at 07:53:25PM +0200, Sedat Dilek wrote:
> >> Files attached.
> >
> > Can you also please attach a full dmesg so I can check for anything
> > unusual?
> >
On 8/13/13 11:59 AM, Randy Dunlap wrote:
> On 08/13/13 01:28, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130812:
>>
>
> on i386:
>
> fs/built-in.o: In function `xfs_log_calc_minimum_size':
> (.text+0x1797a9): undefined reference to `__udivdi3'
>
>
See:
[PATCH] xfs: call roundup_
On Tue, Aug 13, 2013 at 07:53:25PM +0200, Sedat Dilek wrote:
> Files attached.
Can you also please attach a full dmesg so I can check for anything
unusual?
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
--
To unsubscribe from this list: send the line "unsubscribe linux-kern
On Tue, Aug 13, 2013 at 7:13 PM, Chris Wilson wrote:
> On Tue, Aug 13, 2013 at 07:03:44PM +0200, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 6:37 PM, Sedat Dilek wrote:
>> > On Tue, Aug 13, 2013 at 6:34 PM, Chris Wilson
>> > wrote:
>> >> On Tue, Aug 13, 2013 at 06:23:29PM +0200, Sedat Dilek w
On Tue, Aug 13, 2013 at 07:03:44PM +0200, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 6:37 PM, Sedat Dilek wrote:
> > On Tue, Aug 13, 2013 at 6:34 PM, Chris Wilson
> > wrote:
> >> On Tue, Aug 13, 2013 at 06:23:29PM +0200, Sedat Dilek wrote:
> >>> On Tue, Aug 13, 2013 at 5:59 PM, Sedat Dilek
>
On Tue, Aug 13, 2013 at 6:37 PM, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 6:34 PM, Chris Wilson
> wrote:
>> On Tue, Aug 13, 2013 at 06:23:29PM +0200, Sedat Dilek wrote:
>>> On Tue, Aug 13, 2013 at 5:59 PM, Sedat Dilek wrote:
>>> > I have bisected the issue on Linux v3.11-rc5 + drm-intel-nig
On 08/13/13 01:28, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130812:
>
on i386:
fs/built-in.o: In function `xfs_log_calc_minimum_size':
(.text+0x1797a9): undefined reference to `__udivdi3'
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Tue, Aug 13, 2013 at 6:34 PM, Chris Wilson wrote:
> On Tue, Aug 13, 2013 at 06:23:29PM +0200, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 5:59 PM, Sedat Dilek wrote:
>> > I have bisected the issue on Linux v3.11-rc5 + drm-intel-nightly:
>> >
>> > 5456fe3882812aba251886e36fe55bfefb8e8829 is t
On Tue, Aug 13, 2013 at 06:23:29PM +0200, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 5:59 PM, Sedat Dilek wrote:
> > I have bisected the issue on Linux v3.11-rc5 + drm-intel-nightly:
> >
> > 5456fe3882812aba251886e36fe55bfefb8e8829 is the first bad commit
> > commit 5456fe3882812aba251886e36fe55
On Tue, Aug 13, 2013 at 5:59 PM, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 4:45 PM, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 4:07 PM, Sedat Dilek wrote:
>>> On Tue, Aug 13, 2013 at 11:57 AM, Sedat Dilek wrote:
On Tue, Aug 13, 2013 at 11:52 AM, Chris Wilson
wrote:
> On Tu
On Tue, Aug 13, 2013 at 4:45 PM, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 4:07 PM, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 11:57 AM, Sedat Dilek wrote:
>>> On Tue, Aug 13, 2013 at 11:52 AM, Chris Wilson
>>> wrote:
On Tue, Aug 13, 2013 at 11:47:19AM +0200, Sedat Dilek wrote:
On Tue, Aug 13, 2013 at 4:07 PM, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 11:57 AM, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 11:52 AM, Chris Wilson
>> wrote:
>>> On Tue, Aug 13, 2013 at 11:47:19AM +0200, Sedat Dilek wrote:
On Tue, Aug 13, 2013 at 11:39 AM, Chris Wilson
wrot
On Tue, Aug 13, 2013 at 11:57 AM, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 11:52 AM, Chris Wilson
> wrote:
>> On Tue, Aug 13, 2013 at 11:47:19AM +0200, Sedat Dilek wrote:
>>> On Tue, Aug 13, 2013 at 11:39 AM, Chris Wilson
>>> wrote:
>>> > On Tue, Aug 13, 2013 at 11:35:53AM +0200, Sedat Dil
On Tue, Aug 13, 2013 at 11:52 AM, Chris Wilson wrote:
> On Tue, Aug 13, 2013 at 11:47:19AM +0200, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 11:39 AM, Chris Wilson
>> wrote:
>> > On Tue, Aug 13, 2013 at 11:35:53AM +0200, Sedat Dilek wrote:
>> >> After a logout from my "BROKEN" Unity-2D sessio
On Tue, Aug 13, 2013 at 11:47:19AM +0200, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 11:39 AM, Chris Wilson
> wrote:
> > On Tue, Aug 13, 2013 at 11:35:53AM +0200, Sedat Dilek wrote:
> >> After a logout from my "BROKEN" Unity-2D session - the login-screen
> >> for LightDM seems to be OK.
> >> Th
On Tue, Aug 13, 2013 at 11:39 AM, Chris Wilson wrote:
> On Tue, Aug 13, 2013 at 11:35:53AM +0200, Sedat Dilek wrote:
>> After a logout from my "BROKEN" Unity-2D session - the login-screen
>> for LightDM seems to be OK.
>> Then entering my Unity-2D desktop is OK - no screen corruptions.
>
> What ha
On Tue, Aug 13, 2013 at 11:35:53AM +0200, Sedat Dilek wrote:
> After a logout from my "BROKEN" Unity-2D session - the login-screen
> for LightDM seems to be OK.
> Then entering my Unity-2D desktop is OK - no screen corruptions.
What hardware and display do you have?
-Chris
--
Chris Wilson, Intel
On Tue, Aug 13, 2013 at 11:25 AM, Chris Wilson wrote:
> On Tue, Aug 13, 2013 at 11:10:18AM +0200, Sedat Dilek wrote:
>> Hi,
>>
>> with today's next-20130813 I cannot see 1/10 of my desktop-screen's
>> top, it's simply black.
>> I can estimate the URL line in Firefox (or open a new tab blindly and
On Tue, Aug 13, 2013 at 11:10:18AM +0200, Sedat Dilek wrote:
> Hi,
>
> with today's next-20130813 I cannot see 1/10 of my desktop-screen's
> top, it's simply black.
> I can estimate the URL line in Firefox (or open a new tab blindly and
> get a known URL from my autocompleted history).
Can you at
On Tue, Aug 13, 2013 at 11:14 AM, Sedat Dilek wrote:
> On Tue, Aug 13, 2013 at 11:10 AM, Sedat Dilek wrote:
>> On Tue, Aug 13, 2013 at 10:28 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20130812:
>>>
>>> The ext4 tree gained a conflict against Linus' tree.
>>>
>>> The infini
On Tue, Aug 13, 2013 at 10:28 AM, Stephen Rothwell
wrote:
> Hi all,
>
> Changes since 20130812:
>
> The ext4 tree gained a conflict against Linus' tree.
>
> The infiniband tree gained a build failure for which I applied a merge
> fix patch and another so I used the version from next-20130812.
>
>
Hi all,
Changes since 20130812:
The ext4 tree gained a conflict against Linus' tree.
The infiniband tree gained a build failure for which I applied a merge
fix patch and another so I used the version from next-20130812.
The tty tree gained conflicts against the devicetree and tile trees.
The u
Hi all,
Changes since 20120810:
The rr tree gained a conflict against the xtensa tree.
The tty tree lost its build failures.
I have still reverted 3 commits from the signal tree at the request of the
arm maintainer.
49 matches
Mail list logo
