Displaying 4 results from an estimated 4 matches for "data_ref".
Did you mean:
dat_ref
2011 Jul 21
10
[PATCH v5 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup
While testing raid-auto-repair patches I''m going to send out later, I just found
the very last bug in my current scrub patch series:
Changelog v4->v5:
- fixed a deadlock when fixup is taking longer while scrub is about to end
Original message follows:
------------------------
This patch set introduces two new features for scrub. They share the backref
iteration code which is the
2007 Oct 26
2
perl question on CentOS
..../nmap2nagios.pl: line 20: use: command not found
./nmap2nagios.pl: line 22: use: command not found
./nmap2nagios.pl: line 24: use: command not found
./nmap2nagios.pl: line 26: my: command not found
./nmap2nagios.pl: line 29: syntax error near unexpected token `='
./nmap2nagios.pl: line 29: ` $data_ref->{'Path'}) = fileparse($0);'
[root at localhost nmap2nagios-0.1.2]#
When I type in "perl" before the command, I get this:
[root at localhost nmap2nagios-0.1.2]# perl nmap2nagios.pl -v -r
/tmp/nmap.xml -o /tmp/new.cfg
Can't locate XML/Simple.pm in @INC (@INC contains:...
2008 Mar 31
1
[05/17][PATCH] kvm/ia64 : Add head files for kvm/ia64
...+
> +#define _vmm_raw_spin_unlock(x) \
Could you explain the reasoning behind these two macros? Whenever I see
open coded spin lock modifications like these, I have to admit I get a
bit worried.
> +typedef struct kvm_vcpu VCPU;
> +typedef struct kvm_pt_regs REGS;
> +typedef enum { DATA_REF, NA_REF, INST_REF, RSE_REF } vhpt_ref_t;
> +typedef enum { INSTRUCTION, DATA, REGISTER } miss_type;
ARGH! Please see previous mail about typedefs! I suspect this is code
inherited from Xen ? Xen has a lot of really nasty and pointless
typedefs like these :-(
> +static inline void vcpu_set_d...
2008 Mar 31
1
[05/17][PATCH] kvm/ia64 : Add head files for kvm/ia64
...+
> +#define _vmm_raw_spin_unlock(x) \
Could you explain the reasoning behind these two macros? Whenever I see
open coded spin lock modifications like these, I have to admit I get a
bit worried.
> +typedef struct kvm_vcpu VCPU;
> +typedef struct kvm_pt_regs REGS;
> +typedef enum { DATA_REF, NA_REF, INST_REF, RSE_REF } vhpt_ref_t;
> +typedef enum { INSTRUCTION, DATA, REGISTER } miss_type;
ARGH! Please see previous mail about typedefs! I suspect this is code
inherited from Xen ? Xen has a lot of really nasty and pointless
typedefs like these :-(
> +static inline void vcpu_set_d...