public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ubisectech Sirius" <bugreport@ubisectech.com>
To: "Dave Airlie" <airlied@gmail.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
	"maarten.lankhorst" <maarten.lankhorst@linux.intel.com>,
	"mripard" <mripard@kernel.org>,
	"tzimmermann" <tzimmermann@suse.de>,
	"dri-devel" <dri-devel@lists.freedesktop.org>
Subject: 回复:WARNING in drm_mode_create_lease_ioctl
Date: Mon, 17 Jun 2024 14:22:53 +0800	[thread overview]
Message-ID: <bf3fa1c7-5fea-4db6-b7df-e7e19b336f27.bugreport@ubisectech.com> (raw)
In-Reply-To: <CAPM=9twiDQ0Yv8p-oWWWZnnFViMiN79U6VGSC-wisSE-oYOEqg@mail.gmail.com>

> Cc'ing dri-devel

> Does https://lore.kernel.org/dri-devel/20240617035258.2774032-1-airlied@gmail.com/T/#u
> help?

> Thanks,

> Dave.

Hi. The issue does not appear after applied the patch.

> On Mon, 17 Jun 2024 at 13:12, Ubisectech Sirius
> <bugreport@ubisectech.com> wrote:
>>
>> Hello.
>> We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec. Recently, our team has discovered a issue in Linux kernel 6.8.  Attached to the email were a PoC file of the issue.
>>
>> Stack dump:
>>
>> ------------[ cut here ]------------
>> WARNING: CPU: 1 PID: 18929 at mm/page_alloc.c:4545 __alloc_pages+0x402/0x21b0 mm/page_alloc.c:4545
>> Modules linked in:
>> CPU: 1 PID: 18929 Comm: syz-executor.3 Not tainted 6.8.0 #1
>> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
>> RIP: 0010:__alloc_pages+0x402/0x21b0 mm/page_alloc.c:4545
>> Code: ff 00 0f 84 15 fe ff ff 80 ce 01 e9 0d fe ff ff 83 fe 0a 0f 86 0e fd ff ff 80 3d c7 cf 6a 0d 00 75 0b c6 05 be cf 6a 0d 01 90 <0f> 0b 90 45 31 e4 e9 87 fe ff ff e8 5e 3e 9b ff 84 c0 0f 85 7a fe
>> RSP: 0018:ffffc90001cc7808 EFLAGS: 00010246
>> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1ffff92000398f14
>> RDX: 0000000000000001 RSI: 000000000000000b RDI: 0000000000040dc0
>> RBP: ffffc90001cc7ab8 R08: 0000000000000007 R09: 0000000000000000
>> R10: 0000000000000000 R11: 0000000000000000 R12: 00000000007a1200
>> R13: 000000000000000b R14: 0000000000040dc0 R15: 000000000000000b
>> FS:  00007f1717ba5640(0000) GS:ffff88807ec00000(0000) knlGS:0000000000000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 00000000203d0000 CR3: 000000001f5c0000 CR4: 0000000000750ef0
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>> PKRU: 55555554
>> Call Trace:
>>  <TASK>
>>  __alloc_pages_node include/linux/gfp.h:238 [inline]
>>  alloc_pages_node include/linux/gfp.h:261 [inline]
>>  __kmalloc_large_node+0x88/0x1a0 mm/slub.c:3926
>>  __do_kmalloc_node mm/slub.c:3969 [inline]
>>  __kmalloc+0x370/0x480 mm/slub.c:3994
>>  kmalloc_array include/linux/slab.h:627 [inline]
>>  kcalloc include/linux/slab.h:658 [inline]
>>  fill_object_idr drivers/gpu/drm/drm_lease.c:389 [inline]
>>  drm_mode_create_lease_ioctl+0x4ca/0x1f70 drivers/gpu/drm/drm_lease.c:522
>>  drm_ioctl_kernel+0x1eb/0x3f0 drivers/gpu/drm/drm_ioctl.c:744
>>  drm_ioctl+0x582/0xb70 drivers/gpu/drm/drm_ioctl.c:841
>>  vfs_ioctl fs/ioctl.c:51 [inline]
>>  __do_sys_ioctl fs/ioctl.c:871 [inline]
>>  __se_sys_ioctl fs/ioctl.c:857 [inline]
>>  __x64_sys_ioctl+0x1a1/0x210 fs/ioctl.c:857
>>  do_syscall_x64 arch/x86/entry/common.c:52 [inline]
>>  do_syscall_64+0xd5/0x270 arch/x86/entry/common.c:83
>>  entry_SYSCALL_64_after_hwframe+0x6f/0x77
>> RIP: 0033:0x7f1716e8eeed
>> Code: c3 e8 97 2b 00 00 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
>> RSP: 002b:00007f1717ba5028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
>> RAX: ffffffffffffffda RBX: 00007f1716fe3f80 RCX: 00007f1716e8eeed
>> RDX: 00000000200003c0 RSI: 00000000c01864c6 RDI: 0000000000000003
>> RBP: 00007f1716f13014 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 000000000000000b R14: 00007f1716fe3f80 R15: 00007f1717b85000
>>  </TASK>
>>
>>
>> Thank you for taking the time to read this email and we look forward to working with you further.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>

      reply	other threads:[~2024-06-17  6:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  3:12 WARNING in drm_mode_create_lease_ioctl Ubisectech Sirius
2024-06-17  4:05 ` Dave Airlie
2024-06-17  6:22   ` Ubisectech Sirius [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf3fa1c7-5fea-4db6-b7df-e7e19b336f27.bugreport@ubisectech.com \
    --to=bugreport@ubisectech.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox