search for: _never_

Hi, Patch1 add a helper to get virtio_device's status which will be used later. Patch2~4: check virtio_device's status is RTIO_CONFIG_S_ACKNOWLEDGE or not, if so use put_device otherwise use kfree. Patch5: add comments for virtio_register_device help caller do a proper cleanup if got failure. weiping zhang (5): virtio: add helper virtio_get_status virtio_pci: don't kfree device

Hi, Patch1 add a helper to get virtio_device's status which will be used later. Patch2~4: check virtio_device's status is RTIO_CONFIG_S_ACKNOWLEDGE or not, if so use put_device otherwise use kfree. Patch5: add comments for virtio_register_device help caller do a proper cleanup if got failure. weiping zhang (5): virtio: add helper virtio_get_status virtio_pci: don't kfree device

...ovecot.conf is pretty simple, because I just use dovecot for me as the only user. However, when I try to move a 'larger' amount of mails (>200) from my local TB-mbox to the remote IMAPS-storage, the process hangs after about 150 - 160 transferred mails (the 'blocking' mail is _never_ the same). I don't have the slightest clue why - there is nothing in the logs - even if I turn 'verbose_ssl' on. After a while, TB tells me, that the server timed out and dovecot says: "imap(petar): Disconnected" Usually - if I close my MUA correctly - dovecot says: &quo...

...n MSI RS480M2-IL motherboard (ATI Xpress200 chipset) and a Hammer DVD Writer (shows up as a Matshita DVD-RAM SW-9585). Anyway, I downloaded the CentOS 4.3 iso's and burned them to CD. When I boot the new machine it says: Boot CD: DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER I've _never_ seen this error message before. I know this is a RTFM kind of question, but I don't have any idea right now. Any ideas? TIA! Jeff

Hi, I got this issue nailed out. :-D The problem was with the zlib package offered by MinGW. _Never_ use zlib-1.2.3-MSYS-1.0.11.tar.bz2 package, _it's broken_! Instead, download the pre-compiled version of zlib from zlib.net, and use that to build Xapian with MinGW on Windows. Regards, Adi.

...se. Unfortunately it broke again when RH 8.0 > moved to apache 2.0 but that's beside the point - or perhaps > it was the beginning of the new era. Yes, it's a ".0". We've been through this. At this point, I could care less what you think of the 2-2-2, 6-6-6 model. I _never_ said it's the "best." I just said that many of us believe it's the best we know of, and several vendors agree. > What, in fedora, is ever going to be equivalent of that > RH 7.2 -> RH 7.3 transition where features weren't exactly > frozen but there was a focus on...

On Sun, 17 Dec 2017 21:48:05 +0800 weiping zhang <zwp10758 at gmail.com> wrote: > As mentioned at drivers/base/core.c: > /* > * NOTE: _Never_ directly free @dev after calling this function, even > * if it returned an error! Always use put_device() to give up the > * reference initialized in this function instead. > */ > virtio_register_device may fail before/after call device_register, the > caller should do a proper clean...

On Sun, 17 Dec 2017 21:48:05 +0800 weiping zhang <zwp10758 at gmail.com> wrote: > As mentioned at drivers/base/core.c: > /* > * NOTE: _Never_ directly free @dev after calling this function, even > * if it returned an error! Always use put_device() to give up the > * reference initialized in this function instead. > */ > virtio_register_device may fail before/after call device_register, the > caller should do a proper clean...

...But let's say you get #2 to work, now #3 is the biggie. How to you get the OS to "reload" what it thinks is a fixed ATA channel with a fixed drive. Sometimes the FRAID driver does a _poor_ job of it. This is what I see get people all-the-time. In the case of 3Ware cards, the system _never_ -- let me repeat that -- _never_ sees the ATA channel. The system, including the PCI interconnect, _only_ talks to the on-board ASIC. The ASIC then drives the ATA channels. In FRAID, the system, it's CPU and the PCI bus drive and talk _directly_ to the ATA channels. Intelligent RAID uses it...

This series fix the cleanup for the caller of register_virtio_device, the main work is use put_device instead of kfree. V1->V2: * virtio_pci: add comments for the reason use put_device * virtio vop: also use put_device in in _vop_remove_device() weiping zhang (3): virtio_pci: use put_device instead of kfree virtio: use put_device instead of kfree virtio: put reference count of

This series fix the cleanup for the caller of register_virtio_device, the main work is use put_device instead of kfree. V1->V2: * virtio_pci: add comments for the reason use put_device * virtio vop: also use put_device in in _vop_remove_device() weiping zhang (3): virtio_pci: use put_device instead of kfree virtio: use put_device instead of kfree virtio: put reference count of

...9;s different, although the concepts are similiar. There is no vendor that can provide a solution that doesn't need accommodate at some point in a solution. Fortuntely, we don't have the "on-a-whim" changes in the RHEL space like we do in Windows -- _primarily_ _because_ Red Hat _never_ mixes in "new features" mid-release. But configuration management is _always_ an issue. You are _never_ going to eliminate much of it even in the Linux space. It is a necessary evil that you must do -- and that will vary on the focus of the distro. In fact, not doing configuration mana...

On Tue, Dec 12, 2017 at 09:24:02PM +0800, weiping zhang wrote: > As mentioned at drivers/base/core.c: > /* > * NOTE: _Never_ directly free @dev after calling this function, even > * if it returned an error! Always use put_device() to give up the > * reference initialized in this function instead. > */ > so we don't free vp_dev until vp_dev->vdev.dev.release be called. seeing as 5739411acbaa63a6c22c...

On Tue, Dec 12, 2017 at 09:24:02PM +0800, weiping zhang wrote: > As mentioned at drivers/base/core.c: > /* > * NOTE: _Never_ directly free @dev after calling this function, even > * if it returned an error! Always use put_device() to give up the > * reference initialized in this function instead. > */ > so we don't free vp_dev until vp_dev->vdev.dev.release be called. seeing as 5739411acbaa63a6c22c...

As mentioned at drivers/base/core.c: /* * NOTE: _Never_ directly free @dev after calling this function, even * if it returned an error! Always use put_device() to give up the * reference initialized in this function instead. */ virtio_register_device may fail before/after call device_register, the caller should do a proper cleanup. Caller cann't use...

Hello all..... I would like to know if anyone here has had good experience with this Supermicro motherboard.....http://supermicro.com/products/motherboard/P4/E7221/P8SCT.cfm I am thinking about using it in an entry level mail and file server with a 3ware card and 200 GB SATA drives. Cost is a factor here otherwise I would go for an Opteron board instead. JC

...back to idmap.ldb that samba has. The mapping should indeed be consistent for a user on the DC, so it should not intermittently switch between idmap.ldb and the rfc attributes. That would be a bug that we need to understand. One step as written in a previous mail would be to change the dc code to _never_ fall back to idmap.ldb when configured with "idmap_ldb:use rfc2307 = yes". Then you write that when you see the wrong uid, a 'net cache flush' gets you back the correct uid. That is interesting. That flush command flushes winbindd's idmap cache (which is also used r/o by smbd...

...FR- send from time to time voice SMSs with original callerID which means that the call is terminated like a normal call and not recognized as voice SMS. Problem is that we Answer() the call or we forward it or we send it to voicemail, each user having his own setup. In such cases, the SMS will _never_ be delivered as: . after we Answer() the call, the operator send immediately the audio SMS. At this time we are just parsing dialplan to see what to do with the call. If the call is to forward, operator hangup -end of vocal SMS- before the called party could take the call. . if sending to voice...

...nd it from a generic distribution vendor. And you shouldn't wonder why they don't throw in things -- especially not things like Java which are _illegal_ to bundle freely. -- Bryan P.S. As always, maintain your own APT/YUM repository internally, and mix in any required RPMs. I virtually _never_ install from CD/DVD, almost always via NFS -- possibly with some post-install APT/YUM. -- Bryan J. Smith mailto:b.j.smith at ieee.org

Hi, On my x86_64 system I have a SiL311x controller that can do RAID. If I configure my 2 identical disks in a RAID1 setup, I would expect to see only 1 block device on Linux. Still I see 2 block devices. Is this intentional, and if so, isn't that dangerous ? (i.e. writing to both disks at the same time) Anyone with an insight, please explain :) -- dag wieers, dag at wieers.com,