search for: unsafe

...h it 1) I want that the destination directory (on the repository machine) recreate the backed up file path and it permission (I use -R here ) 2) Is there a way to "follow" all the links using -R and -a parameters..?? Currently I am using something like this. rsync -al --delete --copy-unsafe-links --rsh=/usr/bin/ssh -R --delete-excluded -vv --delete /etc/* root@127.0.0.1:/usr/local/src/ Lokk ath some part of the output copying unsafe symlink "/etc/php4/lib" -> "/usr/lib/apache-extramodules" copying unsafe symlink "/etc/rmt" -> "/usr/sbin/rm...

Hal, Thanks for the reply. I am trying to understand the underlying concern. That means the inlining of a callee without unsafe-fp-math attribute set will block the unsafe optimization in its caller, right? Thanks, Yan From: Finkel, Hal J. [mailto:hfinkel at anl.gov] Sent: Tuesday, December 4, 2018 11:34 AM To: Yan Luo <yan.luo2 at synopsys.com>; llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] [Unsafe-fp-math] M...

Hello dev, I have a question about unsafe-fp-math function attribute. Currently LLVM merges this attribute for inlining with logical AND. That means if caller has this attribute set but callee has not, LLVM will reset this attribute on caller. But shouldn't we respect this attribute on caller? If caller wants to perform unsafe fp opera...

...might be looking at keys that are perfectly readable/writable (e.g. to identify Windows version from HKLM/Software/Microsoft/Windows NT/CurrentVersion) and other "corrupted" and irrelevant keys might prevent one from doing so. Changes in v4: * rebase on current master * add HIVEX_OPEN_UNSAFE flag to be used as a guard to enable changes made in these series. This is because heuristic approach is not guaranteed to be always accurate/safe nor is tolerating corrupted blocks when traversing nodes. It's better to have this behavior optional. * make the "hbin" while...

...ts/potato/main/binary-i386/ pool/ In directory dists/potato/main/binary-i386/ is some files symbolic links to ../binary-all/ and some links to ../../../../pool/ In mirror I want preserve links to binary-all/ and copy as files links to pool/. I try use this rsync command: rsync -a --delete --copy-unsafe-links ftp.debian.cz::/debian/dists/potato/ \ /home/debian/potato The result of this is, than all files is copied as regular files and symlinks are not preserved. I wrote test script (attached) which demonstrate error. Is this error fixed in rsync 2.5.5? I try look to archive of mailing list, and...

Go 1.17 or newer is required to use unsafe.Slice(), which in turn allows us to write a simpler conversion from a C array to a Go object during callbacks. To check if this makes sense, look at https://repology.org/project/go/versions compared to our list in ci/manifest.yml, at the time I made this commit: Alpine 3.15: 1.17.10 AlmaLinux 8:...

This used to be a single patch, but I split it into two with the addition of struct Scatterlist. Again a bit new with Rust submissions. I was told by Gary Guo to rebase on top of rust-next, but it seems *very* behind? The first patch does not build on its own due to a dead_code warning. It is hard to not have dead code when one is adding infrastructure to be used by others at a later

Hi all, virsh checks whether a (live) migration is safe or unsafe. When a migration is considered to be unsafe it is rejected unless the --unsafe option is prodivided. As a part of those checks virsh considers the cache settings for the underlying storage resources. In this context only cache="none" is considered to be safe. I wonder why cache="d...

Hi all, A quick question: The current implementation of the "allow unsafe math" option is to specify it via the TargetOptions object. However, this prevents the target-independent optimizer from using it. Are there any opinions (ha!) on how this could be achieved in a nice clean manner which doesn't require using the TargetOptions object in the optimizer? -bw

https://bugzilla.samba.org/show_bug.cgi?id=10989 Bug ID: 10989 Summary: "copying unsafe symlink" warning should not occur if file is not changing Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assig...

I think I share the goal with you to make the foundation for better dead-strip, so thank you for suggesting. I'm not sure if marking a section as a whole as "safe" or "unsafe" is the best approach, though. Some comments. - If the compiler generated code is always "safe", and if we can distinguish it from hand-written assembly code by checking if there's a gap between symbols, can we just assume a section with no gap is always "safe"? - &q...

...Iter { p } } } impl<T: Copy + Clone> Iterator for NullTerminatedIter<T> { - type Item = T; - fn next(&mut self) -> Option<T> { - if self.p.is_null() { + type Item = *const T; + fn next(&mut self) -> Option<*const T> { + let r = unsafe { *(self.p) }; + if r.is_null() { None } else { - let r = unsafe { *(self.p) }; self.p = unsafe { self.p.offset(1) }; Some(r) } } } -fn arg_string_list (v: &Vec<String>) -> Vec<*const i8> { - let...

To continue the discussion I started last year (see the link below) on embedding command-line options in bitcode, I came up with a plan to improve the way the backend changes UnsafeFPMath on a per-function basis. The code in trunk currently resets TargetOptions::UnsafeFPMath at the beginning of SelectionDAGISel::runOnMachineFunction to enable compiling one function with “unsafe-fp-math=true” and another with “unsafe-fp-math=false”, but this won’t work if we want to parallelize...

Hi, as documented, if you use rsync with --copy-unsafe-links, and copy a directory with a symlink pointing outside of the copied tree, the referent of the symlink is copied. Now, assume that the directory contains a symlink, which points to a (2nd) directory outside of the copied tree. If this (2nd) directory contains another symlink, which also point...

Hi, New to this list, but long-time (appreciative) user of rsync. Grateful for any help with my problem here... In particular, I've been having long-standing issues (just now getting around to trying to resolve them) when I use rsync with '--copy-unsafe-links' alongside the '--delete' parameter. If I use either of these two parameters in isolation (along with other shared parameters), I get the expected behavior. However, when I use '--copy-unsafe-links', rsync no longer properly deletes files that are present in the destinat...

...never happen" internal error, like an assert in C. What's the proper way to handle an internal error? > > + } > > ret := make([]uint32, int(count)) > > - // See https://github.com/golang/go/wiki/cgo#turning-c-arrays-into-go-slices > > - // TODO: Use unsafe.Slice() when we require Go 1.17. > > - s := (*[1 << 30]uint32)(unsafe.Pointer(entries))[:count:count] > > Can we require Go 1.17? (current version is 1.20) > > In Go >= 1.17, we can use something like: > > s := unsafe.Slice(C.uint32_t, length) Golang 1.17...

In response to a few private e-mails, here a summary of using Delphi, R-DCOM and R 2.2.0 1) As Earl Glynn noted ( http://finzi.psych.upenn.edu/R/Rhelp02a/archive/50705.html ), there were a few paths specific to my installation in http://www.menne-biomed.de/download/RDComDelphi.zip leading to path errors on compilation. Hopefully, this has been corrected in the new zip file. 2) Always check if

On 7/25/2013 3:56 PM, Rui Ueyama wrote: > I think I share the goal with you to make the foundation for better > dead-strip, so thank you for suggesting. I'm not sure if marking a section > as a whole as "safe" or "unsafe" is the best approach, though. Some > comments. > > - If the compiler generated code is always "safe", and if we can > distinguish it from hand-written assembly code by checking if there's a gap > between symbols, can we just assume a section with no gap is alway...

Hi list, I would like to understand if, and why, the --unsafe flag is needed when using --copy-storage-all when migrating guests which uses writeback cache mode. Background: I want to live migrate guests with writeback cache from host A to host B and these hosts only have local storage (ie: no shared storage at all). From my understanding, --unsafe sho...

The patch from 2-1/2 years ago for changing copy-unsafe-links to follow unsafe links on the destination side also included essentially this patch. When I looked at it, however, I asked why in the world is unsafe_symlink() doing strdup() in the first place. I think you could get rid of the calls to strdup() and the new local variables and possibly do a...