search for: read_on

...opyright (C) 2018 Red Hat Inc. +# Copyright (C) 2018-2019 Red Hat Inc. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are @@ -94,8 +94,8 @@ case "$1" in esac EOF -[ $eflags -eq $(( HAS_FLAGS|READ_ONLY|SEND_DF )) ] || - fail "expected HAS_FLAGS|READ_ONLY|SEND_DF" +[ $eflags -eq $(( HAS_FLAGS|READ_ONLY|SEND_DF|SEND_CACHE )) ] || + fail "expected HAS_FLAGS|READ_ONLY|SEND_DF|SEND_CACHE" #---------------------------------------------------------------------- # -r @@ -10...

...OTHERWISE) ARISING IN ANY WAY OUT +# OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. + +# Test export flags. +# +# Run nbdkit with various can_* callbacks defined and with or without +# the -r flag, and check that nbdkit constructs the export flags +# controlling READ_ONLY, ROTATIONAL, SEND_TRIM, etc. as expected. +# +# We use the oldstyle (-o) protocol here because it's simpler to read +# out the eflags. We use the shell plugin because it gives maximum +# control over the can_* callbacks (at least, max without having to +# write a C plugin). + +source ./funct...

...yone used both? That person would have great authority... With mysql-proxy, I''m getting no reads on the readonly slave, only message I''m getting is "no handler for COM_CONNECT" grr With acts_as_readonlyable, I''m getting: "No db config entry defined for read_only" Here''s my config/database.yml (some names changed to protect the innocent): production: database: master_db adapter: mysql database: mydb_production username: myusr password: ******* host: *.*.*.96 encoding: utf8 read_only: database: read_only adapter: mysql d...

.../btrfs/disk-io.c +++ b/fs/btrfs/disk-io.c @@ -43,6 +43,8 @@ static struct extent_io_ops btree_extent_io_ops; static void end_workqueue_fn(struct btrfs_work *work); static void free_fs_root(struct btrfs_root *root); +static void btrfs_check_super_valid(struct btrfs_fs_info *fs_info, + int read_only); /* * end_io_wq structs are used to do processing in task context when an IO is @@ -1700,6 +1702,11 @@ struct btrfs_root *open_ctree(struct super_block *sb, if (!btrfs_super_root(disk_super)) goto fail_iput; + /* check filesystem state */ + fs_info->fs_state |= btrfs_super_flags(d...

...*****/ + struct shmem_ops *sysv_shm_open(int ronly) { BOOL other_processes; @@ -536,6 +537,8 @@ union semun su; int i; pid_t pid; + struct passwd *root_pwd = sys_getpwuid((uid_t)0); + gid_t root_gid = root_pwd ? root_pwd->pw_gid : (gid_t)0; read_only = ronly; @@ -593,7 +596,7 @@ hash_size = sem_ds.sem_nsems-1; if (!read_only) { - if (sem_ds.sem_perm.cuid != 0 || sem_ds.sem_perm.cgid != 0) { + if (sem_ds.sem_perm.cuid != 0 || sem_ds.sem_perm.cgid != root_gid) { DEBUG(0,(&q...

...| 2 +- 11 files changed, 47 insertions(+), 32 deletions(-) diff --git a/fish/fish.c b/fish/fish.c index dd73af7..bc518da 100644 --- a/fish/fish.c +++ b/fish/fish.c @@ -474,10 +474,13 @@ mount_mps (struct mp *mp) if (mp) { mount_mps (mp->next); - if (!read_only) - r = guestfs_mount (g, mp->device, mp->mountpoint); - else - r = guestfs_mount_ro (g, mp->device, mp->mountpoint); + + /* Don't use guestfs_mount here because that will default to mount + * options -o sync,noatime. For more information, see guestfs(3) +...

I'm still working my way through the filters before this series will be complete, but this is enough of a start to at least get some feedback on the idea of implementing another NBD protocol extension. Eric Blake (9): server: Internal hooks for implementing NBD_CMD_CACHE plugins: Add .cache callback file, split: Implement .cache with posix_fadvise nbd: Implement NBD_CMD_CACHE

...re---------------------------------------------------------------- diff -urN rsync-2.5.2.orig/loadparm.c rsync-2.5.2/loadparm.c --- rsync-2.5.2.orig/loadparm.c Sun Dec 2 09:16:15 2001 +++ rsync-2.5.2/loadparm.c Sat Feb 23 13:48:12 2002 @@ -117,6 +117,7 @@ char *comment; char *lock_file; BOOL read_only; + BOOL write_only; BOOL list; BOOL use_chroot; BOOL transfer_logging; @@ -149,6 +150,7 @@ NULL, /* comment */ DEFAULT_LOCK_FILE, /* lock file */ True, /* read only */ + False, /* write only */ True, /* list */ True, /* use chroot */ False, /* transfer logging...

Rich pointed out that making thread_model dynamic even for plugins makes some sense, so here is the code for doing it for 'sh'. I'm less confident on how to do it for OCaml and Rust (not to mention that those allow the plugin to already compile in their model, rather than the language binding glue forcing a model). The other languages (lua, perl, python, ruby) still need to be

...* completely resets the 'conf' structure. This means we cannot - * call config_read twice on the two possible configuration - * files, but instead have to copy out settings into our - * variables between calls. - * - * (2) If the next call fails then 'read_only' variable is not - * updated. Failure could happen just because the setting is - * missing from the configuration file, so we ignore it here. - */ - config_lookup_bool (&conf, "read_only", &read_only); - } - } + config_init (&conf); - fp...

...iles > 2GB to an AIX machine. Here is a fix: diff -c -r rsync-2.5.6.orig/syscall.c rsync-2.5.6/syscall.c *** rsync-2.5.6.orig/syscall.c Sun Jan 26 21:09:02 2003 --- rsync-2.5.6/syscall.c Wed May 14 13:55:15 2003 *************** *** 151,157 **** if (dry_run) return -1; if (read_only) {errno = EROFS; return -1;} ! #if defined(HAVE_SECURE_MKSTEMP) && defined(HAVE_FCHMOD) { int fd = mkstemp(template); if (fd == -1) return -1; --- 151,157 ---- if (dry_run) return -1; if (read_only) {errno = EROFS; return -1;}...

Some feature additions to the shell script plugin allow us to test the export flags field reasonably easily. Rich.

I have activerecord-sybase-adapter installed -- and Sybase itself, so I have the drivers. In irb or in the rails console, this works: ActiveRecord::Base.establish_connection( :adapter => “sybase”, :database => “mydb”, :host => “myhost”, :myport => myport, :username => “read_only”, :password => “read_only”) In Rails, I have this in my database.yml: pacs: adapter: sybase database: mydb username: read_only password: read_only host: myhost port: myport And then I have the following model: class PacsPatient < ActiveRecord::Base establish_connection &quo...

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

v1 was here: https://www.redhat.com/archives/libguestfs/2018-December/thread.html#00123 v2: - Document "-" instead of "script=-" and use it in the test; and verify this also works on FreeBSD; and verify that it doesn't depend on the particular behaviour of our wrapper script and should work with installed nbdkit too. - Fix handling of zero flags parameter. -

...echo echo "Minimal reproducible example (MRE)" echo "----------------------------------" echo echo "Tested with" echo "- rsync version 3.2.7 protocol version 31" echo "- ext4 file system" echo rm -rf MRE mkdir MRE cd MRE mkdir source touch source/read_only.txt chmod 444 source/read_only.txt mkdir snapshot1 # rsync --recursive --times --devices --specials --hard-links --human-readable -s --links --perms --executability --group --owner source/* snapshot1/ rsync --perms --executability --group --owner source/* snapshot1/ mkdir snapshot2 # rsync --re...

Marking volatile accesses as !unordered seems excessively conservative. For instance, LLVM is not able to optimize declare void @escape(i32*) declare i32 @read_only(i32) readonly define i32 @f(i1* %c) { entry: %a = alloca i32 %b = alloca i32 call void @escape(i32* %a) call void @escape(i32* %b) %a0 = load i32, i32* %b, align 4 %lv = load volatile i32, i32* %b %a1 = load i32, i32* %a, align 4 %result = add i32 %a0, %a1 ret i32 %result }...

...Did my script attached to the initial post here reproduce the permission change? PS: In my case the attached script shows (excerpt): ./setup_cp_al.sh Tested with - rsync version 3.2.7 protocol version 31 - ext4 file system - Ubuntu 22.04 File stats BEFORE rsync --delete: File: snapshot2/read_only.txt Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: 10305h/66309d Inode: 17571021 Links: 3 Access: (0444/-r--r--r--) Uid: ( 1000/ user1) Gid: ( 1000/ user1) Access: 2023-09-22 20:51:16.690961150 +0200 Modify: 2023-09-22 20:51:16.690961150 +0200 Change: 2023...

...sv.c Tue Aug 10 16:10:18 1999 +++ shmem_sysv.c.fixed Tue Aug 10 16:08:16 1999 @@ -536,6 +536,8 @@ union semun su; int i; pid_t pid; + struct passwd *root_pwd = sys_getpwuid((uid_t)0); + gid_t root_gid = root_pwd ? root_pwd->pw_gid : (gid_t)0; read_only = ronly; @@ -593,8 +595,8 @@ hash_size = sem_ds.sem_nsems-1; if (!read_only) { - if (sem_ds.sem_perm.cuid != 0 || sem_ds.sem_perm.cgid != 0) { - DEBUG(0,("ERROR: root did not create the semaphore\n")); + if (sem_ds.se...