| 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
| ||
|
Message-ID: <20110127152926.GA4898@redhat.com> Date: Thu, 27 Jan 2011 17:29:26 +0200 From: "Michael S. Tsirkin" <mst@...hat.com> To: Christoph Hellwig <hch@....de> Cc: Rusty Russell <rusty@...tcorp.com.au>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] virtio_blk: allow re-reading config space at runtime On Wed, Jan 19, 2011 at 12:54:01AM +0100, Christoph Hellwig wrote: > On Wed, Jan 19, 2011 at 09:56:09AM +1030, Rusty Russell wrote: > > > I don't think we have much choice. We're getting called from irq > > > context, so we'll need to allocate memory to offload things. That's > > > unless we keep a thread around that we just need to wake up, which > > > would be a huge waste of ressources. > > > > Yes, but can we keep a workqueue struct around? > > We can keep one around, but we can't prevent the virtio core code from > calling us again while it's still in use. Yes but in that specific situation (double schedule before it runs once) discarding one change notification would not hurt at all. > -- > 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/ > -- 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/
Powered by blists - more mailing lists