linux-kernel - Re: sparc/staging compile error

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: <4913FEE1.9030807@bravegnu.org>
Date:	Fri, 07 Nov 2008 14:10:01 +0530
From:	Vijay Kumar <vijaykumar@...vegnu.org>
To:	"J.R. Mauro" <jrm8005@...il.com>
CC:	Christoph Hellwig <hch@...radead.org>,
	Paul Mackerras <paulus@...ba.org>, Greg KH <greg@...ah.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	LKML <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>,
	"William L. Irwin" <wli@...omorphy.com>, jayakumar.lkml@...il.com,
	sparclinux@...r.kernel.org
Subject: Re: sparc/staging compile error

J.R. Mauro wrote:
> On Thu, Nov 6, 2008 at 12:32 PM, Christoph Hellwig <hch@...radead.org> wrote:
>> On Thu, Nov 06, 2008 at 09:06:36AM -0500, J.R. Mauro wrote:
>>> static int poch_ioctl(struct inode *inode, struct file *filp,
>>>                       unsigned int cmd, unsigned long arg)
>>> {
>>> /* ---snip---*/
>>>         case POCH_IOC_SYNC_GROUP_FOR_USER:
>>>         case POCH_IOC_SYNC_GROUP_FOR_DEVICE:
>>>                 vms = find_vma(current->mm, arg);
>>>                 if (!vms)
>>>                         /* Address not mapped. */
>>>                         return -EINVAL;
>>>                 if (vms->vm_file != filp)
>>>                         /* Address mapped from different device/file. */
>>>                         return -EINVAL;
>>>
>>>                 flush_cache_range(vms, arg, arg + channel->group_size);
>> This doesn't look like something a driver should ever do.  Could someone
>> explain what it's trying to do from a high level point of view?
>
> CC'd driver maintainers mentioned in the README

May be the code is not doing what is supposed to do, but here is what the 
driver is trying to achieve:

The driver allocates a set of buffers for DMA. These buffers are mapped 
into user space, when the user does an mmap. In transmit, when the user 
space writes to these buffers, the data has to reach physical memory so 
that the device can access them. For receive, the cache has to be 
invalidated before the user space reads the buffer.

Do let me know if further clarification is required. Any inputs and 
suggestions are welcome.

BTW, please do send in the compiler error message.

Regards,
Vijay
--
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/