search for: get_uids

On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote: > This change adds a new flavor of dma-bufs that can be used by virtio > drivers to share exported objects. A virtio dma-buf can be queried by > virtio drivers to obtain the UUID which identifies the underlying > exported object. > > Signed-off-by: David Stevens <stevensd at chromium.org> Is this just for

On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote: > This change adds a new flavor of dma-bufs that can be used by virtio > drivers to share exported objects. A virtio dma-buf can be queried by > virtio drivers to obtain the UUID which identifies the underlying > exported object. > > Signed-off-by: David Stevens <stevensd at chromium.org> Is this just for

Hi, I''m having a problem getting past the authentication mechanism in rails using my controller functional tests. my functional tests look like this def test_4 $stdout.puts ''TEST 4: cookies is '' + cookies.to_s # :user => {:id => users(:testuser).id} cookies[:user_id] = ''2222'' $stdout.puts ''1. cookies is ''

On Tue, Aug 18, 2020 at 04:13:41PM +0900, David Stevens wrote: > This change adds a new flavor of dma-bufs that can be used by virtio > drivers to share exported objects. A virtio dma-buf can be queried by > virtio drivers to obtain the UUID which identifies the underlying > exported object. > > Signed-off-by: David Stevens <stevensd at chromium.org> This makes VIRTIO

...ransaction_begin>, transaction_commit = 0x336b0 <mbox_transaction_commit>, transaction_rollback = 0x337a8 <mbox_transaction_rollback>, keywords_create = 0x44650 <index_keywords_create>, keywords_free = 0x44668 <index_keywords_free>, get_uids = 0x3f37c <index_storage_get_uids>, mail_alloc = 0x4076c <index_mail_alloc>, header_lookup_init = 0x421f0 <index_header_lookup_init>, header_lookup_deinit = 0x423a8 <index_header_lookup_deinit>, search_get_sorting = 0x437fc <index_storage_s...

Hi David, On Fri, Jun 19, 2020 at 10:57:37AM +0900, David Stevens wrote: > On Thu, Jun 18, 2020 at 9:29 PM Guennadi Liakhovetski > <guennadi.liakhovetski at linux.intel.com> wrote: > > > > Hi Michael, > > > > On Thu, Jun 04, 2020 at 03:05:23PM -0400, Michael S. Tsirkin wrote: > > > On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote: >

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

I've been doing some stress testing in the last few days and fixing all the errors I saw. I'm hoping that I've finally really fixed all the index/mbox problems. So, again I think the only thing left for v1.0 is the documentation. Please test this nightly snapshot before I'll release rc27 tomorrow: http://dovecot.org/nightly/dovecot-latest.tar.gz If you've seen any of the

...= 0x3505c <mbox_transaction_begin>, transaction_commit = 0x34f44 <mbox_transaction_commit>, transaction_rollback = 0x34efc <mbox_transaction_rollback>, keywords_create = 0x4d514 <index_keywords_create>, keywords_free = 0x4d4fc <index_keywords_free>, get_uids = 0x48d2c <index_storage_get_uids>, mail_alloc = 0x4a3b8 <index_mail_alloc>, header_lookup_init = 0x4a6cc <index_header_lookup_init>, header_lookup_deinit = 0x4a6b0 <index_header_lookup_deinit>, search_get_sorting = 0x4c000 <index_storage_search_get_sortin...

As promised, here it is finally. v1.0 is getting nearer and I want people to start looking at Dovecot's sources. Getting some more help with development would be nice, but I'd also like to hear if there are any hidden bugs in the code. So, one week from now I'll start offering 1000 EUR for the first person to point out a remotely exploitable security hole in Dovecot. See