linux-kernel - Re: MMC core debugfs support (was Re: [RFC v2 5/5] Atmel MCI: Driver for Atmel on-chip MMC controllers)

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

Message-ID: <20080225181214.0860f622@mjolnir.drzeus.cx>
Date:	Mon, 25 Feb 2008 18:12:14 +0100
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Haavard Skinnemoen <hskinnemoen@...el.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: MMC core debugfs support (was Re: [RFC v2 5/5] Atmel MCI:
 Driver for Atmel on-chip MMC controllers)

On Thu, 14 Feb 2008 15:00:05 +0100
Haavard Skinnemoen <hskinnemoen@...el.com> wrote:

> 
> I've started working on this, but I've run into a problem: The mmc core
> structures don't seem to keep any references to the current request. So
> I don't really have any information to put into the 'req' file after
> moving it into the core.
> 
> Any ideas on how to solve this?
> 

The simple solution is just to add it. :)

But is it needed though? Shouldn't a read block until there is an event, at which point you'll have access to the data structures long enough to output data.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org
--
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/