linux-kernel - Re: [PATCH 1/4] dmaengine: add a release for dma class devices and dependent infrastructure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081203170741.7f25d756@extreme>
Date:	Wed, 3 Dec 2008 17:07:41 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Dan Williams <dan.j.williams@...el.com>
Cc:	linux-kernel@...r.kernel.org,
	Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
	Alexander Beregalov <a.beregalov@...il.com>
Subject: Re: [PATCH 1/4] dmaengine: add a release for dma class devices and
 dependent infrastructure

On Wed, 03 Dec 2008 17:46:46 -0700
Dan Williams <dan.j.williams@...el.com> wrote:

> Resolves:
> WARNING: at drivers/base/core.c:122 device_release+0x4d/0x52()
> Device 'dma0chan0' does not have a release() function, it is broken and must be fixed.
> 
> The dma_chan_dev object is introduced to gear-match sysfs kobject and
> dmaengine channel lifetimes.  When a channel is removed access to the
> sysfs entries return -ENODEV until the kobject can be released.
> 
> The bulk of the change is updates to existing code to handle the extra
> layer of indirection between a dma_chan and its struct device.
> 
> Reported-by: Alexander Beregalov <a.beregalov@...il.com>
> Cc: Stephen Hemminger <shemminger@...tta.com>
> Cc: Haavard Skinnemoen <haavard.skinnemoen@...el.com>
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>

Much better thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/