linux-kernel - [Query] Using DMA API's with struct dev created from device

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>] [day] [month] [year] [list]

Message-ID: <CABPxzYKNo7rs1TiF=EbQLQpUfuVtJH442eFLqs1Bmz_n_n2Jqg@mail.gmail.com>
Date:	Thu, 7 Nov 2013 14:19:40 +0530
From:	Krishna Chaitanya <chaitanya.mgit@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	Krishna Chaitanya <chaitanya.mgit@...il.com>
Subject: [Query] Using DMA API's with struct dev created from device_create

Hi,

In cases where the BUS interface is system fabric itself,
where no probing is required, so kernel doesn't provide the
"dev" pointer (unlike USB and PCI). The driver is a wireless
driver based on mac80211.

So we used device_create to device, which is passed to
set_wiphy_dev, it works fine.

But when we pass the same device to dma_map_single it
is causing a system panic and reboot (no call stack), instead
if i pass NULL it works just fine.

How do we deal with "struct dev" in such cases?

-- 
Thanks,
Regards,
Chaitanya T K.
P.S. Please CC me to the replies.
--
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/