search for: bandaid

...tion, and should never have been accepted into the IR in the first place. IIUC, both “undef” and “poison” share this undesirable definition for which “freeze” is proposed as a fix, but if I understand your logic correctly there is no way to fix this example with “freeze” ? IMHO "freeze” is a bandaid over a bad definition, that doesn’t seem to solve the inlining problem, and we should fix the definition rather than add a bandaid. Peter Lawrence.

Last patch for now. This gets gen_init_cpio into a state where it can pick up a "kinit" binary from usr and stuff it into the cpio archive as /sbin/init. This is obviously a crock, but it suffices for testing until something sane is done about integrating klibc into the kernel tree. The patch also adds a bit of instrumentation to initramfs.c, to try to help flush out bug 740.

...'') --> should use custom_env and custom_release to help determine where the variable is defined in hiera. Are custom facts from non root users simply not relayed to hiera? :hierarchy: - nodes/%{::fqdn} - releases/%{custom_release} - env/%{custom_env} - common I have put a bandaid fix in for now which sets these variables via top scope assignment in one of my classes and allows me to control everything from hiera instead of using custom facts. However, I am not sure if this follows good puppet coding practices when using hiera, since I am using hiera to feed hiera. I don...

On Wednesday 04 October 2017 12:54:44 Mark Haney wrote: > Sorry, but if you have to use packages that don't originate from CentOS > and they do that, then I wouldn't use them. Period.? I'd compile from > source before I used something configured that way. This perspective to some extent employs cutting your nose of dispite youre face. Before Packages were introduced,

Greetings, Kernel bound workloads seem to trigger the below for whatever reason.  I only see this when beating up NFS.  There was a kworker wakeup latency issue, but with a bandaid applied to fix that up, I can still trigger this. [ 1313.811031] nouveau 0000:01:00.0: swiotlb buffer is full (sz: 2097152 bytes) [ 1313.811035] swiotlb: coherent allocation failed for device 0000:01:00.0 size=2097152 [ 1313.811038] CPU: 6 PID: 3026 Comm: Xorg Tainted: G E 4.15.0.g12...

...8:01 PM, Tobias Klausmann wrote: > On 12/18/17 7:06 PM, Mike Galbraith wrote: >> Greetings, >> >> Kernel bound workloads seem to trigger the below for whatever reason. >>   I only see this when beating up NFS.  There was a kworker wakeup >> latency issue, but with a bandaid applied to fix that up, I can still >> trigger this. > > > Hi, > > i have seen this one as well with my system, but i could not find an > easy way to trigger it for bisecting purpose. If you can trigger it > conveniently, a bisect would be nice! I'm seeing this (w...

...ar: Please explain how compiling packages yourself turns such packages into standard packages. > THIS. IS. NOT. ACCEPTABLE. It is not acceptable to create the system in such a way that files indiscriminately disappear, without any check whatsoever if that?s ok. > The fact you'd rather bandaid a problem (in production no less) than > follow proper standards or compile from source to avoid said bandaid > would be a fire-able offense in any IT shop I've ever worked at. Did they require you to verify all the sources of packages you compiled yourself to make sure that they behave...

...12/18/17 7:06 PM, Mike Galbraith wrote: >>>> Greetings, >>>> >>>> Kernel bound workloads seem to trigger the below for whatever reason. >>>>   I only see this when beating up NFS.  There was a kworker wakeup >>>> latency issue, but with a bandaid applied to fix that up, I can still >>>> trigger this. >>> >>> Hi, >>> >>> i have seen this one as well with my system, but i could not find an >>> easy way to trigger it for bisecting purpose. If you can trigger it >>> conveniently,...

...n use. > > > > Of course, it might stay used forever, so it's an extremely ugly hack, > > but it seems better than use-after-free that we have now. > > > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > > I'll apply it, but it looks like a bandaid. Absolutely. > The right answer would seem to be: > 1) Use reference counting: 1 for client, 1 for transport. > 2) When hot unplug, complete (ie. fail) all outstanding requests. > 3) From then on, fail all incoming requests. > 4) When refcount hits 0, free the structure. > &gt...

...n use. > > > > Of course, it might stay used forever, so it's an extremely ugly hack, > > but it seems better than use-after-free that we have now. > > > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > > I'll apply it, but it looks like a bandaid. Absolutely. > The right answer would seem to be: > 1) Use reference counting: 1 for client, 1 for transport. > 2) When hot unplug, complete (ie. fail) all outstanding requests. > 3) From then on, fail all incoming requests. > 4) When refcount hits 0, free the structure. > &gt...

...>>>>> Greetings, > >>>>> > >>>>> Kernel bound workloads seem to trigger the below for whatever reason. > >>>>> I only see this when beating up NFS. There was a kworker wakeup > >>>>> latency issue, but with a bandaid applied to fix that up, I can still > >>>>> trigger this. > >>>> > >>>> > >>>> Hi, > >>>> > >>>> i have seen this one as well with my system, but i could not find an > >>>> easy way to trigge...

...anymore. > Since I have no answer to the problem described above, it means that > the only solution is: > > $ echo /bin/systemctl restart winbind |sudo dd of=/etc/cron.daily/restart-wbind > $ sudo chmod 755 /etc/cron.daily/restart-wbind > > Many thanks > That is a bandaid over a problem. Can you explain why your PDC smb.conf seems to be a mixture of a PDC one and an ADS domain member one ? You do not actually need winbind on an NT-4 style PDC and this could be a part of your problem. Have a look here for a bare PDC setup: http://xmodulo.com/samba-primary-domain-...

...in production environments is far more acceptable than compiling from source because of package management 'benefits' then (to me anyway) you're lazy and dangerous with critical data.? My statement still stands.? Let me be clear: THIS. IS. NOT. ACCEPTABLE. The fact you'd rather bandaid a problem (in production no less) than follow proper standards or compile from source to avoid said bandaid would be a fire-able offense in any IT shop I've ever worked at. > Package managers got round (mostly) both the dependancy problem and updating > too. The problem with package mai...

Drivers have no business looking into dma-mapping internals and check what backend is used. Unfortunstely the DRM core is still broken and tries to do plain page allocations instead of using DMA API allocators by default and uses various bandaids on when to use dma_alloc_coherent. Switch nouveau to use the same (broken) scheme as amdgpu and radeon to remove the last driver user of is_swiotlb_active. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/gpu/drm/nouveau/nouveau_ttm.c | 10 +++------- 1 file changed, 3 inserti...

Hey, the following line in fstab used to work just fine for my /tmp: tmpfs /tmp tmpfs rw,size=1g,mode=1777 0 0 But since I upgraded to 8.2-PRERELEASE, /tmp will soon run out of space (usually after leaving the box overnight). % df /tmp Filesystem 1K-blocks Used Avail Capacity Mounted on tmpfs 12 12 0 100% /tmp Yes, what you see here, is not

...something about this, as they are releasing a FAX module similar to app_fax. It looks like they have. In chan_dahdi.c there is now code that extends the buffering inside dadhi when a FAX is detected, and puts the buffering back to normal at the end. This isn't really a cure - its more of a bandaid. However, I expect it has the desired effect if they have put it into the trunk code. You need to enable this feature in chan_dahdi.conf. The current default chan_dahdi.conf has the following line ;faxbuffers=>6,full You will need to remove the ";" to make the feature work. I doub...

...before that point, the child process simply locks up. This suggests that hack workaround of adding a call to say msleep(30) just before the line kill(pid, SIGUSR2) in main.c:do_recv(). With that kludge in, I haven't seen any hangs in a few hundred trials. YMMV, but it might be a helpful bandaid until some cygwin expert has the chance fix things properly. Rgds Anthony This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All ma...

...R in the first place. >> >> IIUC, both “undef” and “poison” share this undesirable definition >> for which “freeze” is proposed as a fix, but if I understand your >> logic correctly there is no way to fix this example with “freeze” ? >> >> IMHO "freeze” is a bandaid over a bad definition, that doesn’t >> seem to solve the inlining problem, and we should fix the definition >> rather than add a bandaid. >> >> >> Peter Lawrence. >> _______________________________________________ >> LLVM Developers mailing list >> ll...

...address is sent.  But there's not enough detail in the debugs to see why this decision was not made to use external_media_address By default we use nat settings for all our endpoints, but obviously it's not required here for an ITSP that has trustworthy media ports in the SDP.  Maybe a bandaid is turning off rewrite_contact for this endpoint?  Going to try that as soon as possible. Why is external_media_address not being used all of a sudden?  Has anyone else seen this... is this a bug? -------------- next part -------------- A non-text attachment was scrubbed... Name: debug.log Type:...

On device hot-unplug, 9p/virtio currently will kfree channel while it might still be in use. Of course, it might stay used forever, so it's an extremely ugly hack, but it seems better than use-after-free that we have now. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- net/9p/trans_virtio.c | 25 +++++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-)