From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 123F5C433E2 for ; Fri, 10 Jul 2020 13:51:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E2FAA20767 for ; Fri, 10 Jul 2020 13:51:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kernel-dk.20150623.gappssmtp.com header.i=@kernel-dk.20150623.gappssmtp.com header.b="VqgkTfuU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728110AbgGJNvV (ORCPT ); Fri, 10 Jul 2020 09:51:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37982 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727780AbgGJNvU (ORCPT ); Fri, 10 Jul 2020 09:51:20 -0400 Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 69F18C08C5DC for ; Fri, 10 Jul 2020 06:51:20 -0700 (PDT) Received: by mail-io1-xd44.google.com with SMTP id e64so6037459iof.12 for ; Fri, 10 Jul 2020 06:51:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=QeRVYBt393FV/Oy9pMvr9BzFrA2Q5Owg6rz86iAAWvE=; b=VqgkTfuUQIcolaNHige2EiKE+2/CTrpTLBXlNHkj1GNhd0yPvPs/rsMb22SsAuQ/1i A5kpASJycDfU0lbTd/SpKfYLz2ZLowaOGTagkeRszZroijTZWTbd7ghljYnqIfkxMO6R dKV11gpnG+BgwvHYPLzJw9thHUnn23e4Vqyc16b1Pt2zmV7nikEFzDlLV2iS9AyzkHSc OEgJtEV6eYALfaTbs4uX2+0MvJ4efqCNYyd8wAhlGIiWve6vmV6KAXm3zPf2eKs0QLL/ NyDMjhMfLqyvb965h74p/V86AAWMQdgiJmeSZTABomzPgkPeBmz5aAbCH2BRSCPf9/nZ sNfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QeRVYBt393FV/Oy9pMvr9BzFrA2Q5Owg6rz86iAAWvE=; b=r+1WZc1UMd5kR5O+I5cktl2yMOFdCLiXLT/fe6IQhU9ssqC51e6982dleFDi5CUXmB 9aPkMG1eNv84GUdW6Zk1ftCONVMVMuOJwIjPY0cYVuC18kzVJuSNU4uP8vFoj1esgqT/ 6WWBHY2XzIrVntvpeL+I6WP5giLW7tFxuhBwGbns2iiy2sSWJHr8gGbs6q1unsUthICn Wkjo3XebDSoL1RUEaR2d/zIuUOPkAePXRWJ6+20UkbFZkcot2Hgf8H5dTtzVB0UI4+gL PHEnRfrPeuT16DbiHwuXlfpeO1i40tCBmPI7DWEh4K/kLpqVTMB89+hPEJXynNmvFVce UXvg== X-Gm-Message-State: AOAM530c0TwCbEBFTwcWoRgqsQPq5Q3nDBRyGJ9+z9NeSRrmKoxrXHlN lLdbD0PiY+vIhcmElrOeIfzicvWVhT7naw== X-Google-Smtp-Source: ABdhPJwt1qfIrP+mCXUhdLt9LSYLo0v7L6vhgNKaZKXOlsiRI441lAOnv681pvZAX3lENvsiALwJOQ== X-Received: by 2002:a6b:8d4d:: with SMTP id p74mr440340iod.173.1594389079396; Fri, 10 Jul 2020 06:51:19 -0700 (PDT) Received: from [192.168.1.58] ([65.144.74.34]) by smtp.gmail.com with ESMTPSA id c29sm3652762ilg.53.2020.07.10.06.51.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Jul 2020 06:51:18 -0700 (PDT) Subject: Re: [PATCH] io_uring: fix memleak in io_sqe_files_register() To: Yang Yingliang , io-uring@vger.kernel.org, linux-kernel@vger.kernel.org References: <20200710141420.3987063-1-yangyingliang@huawei.com> From: Jens Axboe Message-ID: <65c82eaf-3f95-9280-3dc4-25b9e0781213@kernel.dk> Date: Fri, 10 Jul 2020 07:51:18 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200710141420.3987063-1-yangyingliang@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/10/20 8:14 AM, Yang Yingliang wrote: > I got a memleak report when doing some fuzz test: > > BUG: memory leak > unreferenced object 0x607eeac06e78 (size 8): > comm "test", pid 295, jiffies 4294735835 (age 31.745s) > hex dump (first 8 bytes): > 00 00 00 00 00 00 00 00 ........ > backtrace: > [<00000000932632e6>] percpu_ref_init+0x2a/0x1b0 > [<0000000092ddb796>] __io_uring_register+0x111d/0x22a0 > [<00000000eadd6c77>] __x64_sys_io_uring_register+0x17b/0x480 > [<00000000591b89a6>] do_syscall_64+0x56/0xa0 > [<00000000864a281d>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 > > > Call percpu_ref_exit() on error path to avoid > refcount memleak. Applied, thanks. -- Jens Axboe