-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pete/Piet Delaney wrote:
> Jason Wessel wrote:
>> Andrew Morton wrote:
>>> On Wed, 22 Aug 2007 17:44:12 -0500
>>> Jason Wessel <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>> +while (!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pete/Piet Delaney wrote:
> Jason Wessel wrote:
>> Andrew Morton wrote:
>>> On Wed, 22 Aug 2007 17:44:12 -0500
>>> Jason Wessel <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>> +while (!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Wessel wrote:
> Andrew Morton wrote:
>> On Wed, 22 Aug 2007 17:44:12 -0500
>> Jason Wessel <[EMAIL PROTECTED]> wrote:
>>
>>
>>> +while (!atomic_read(_active));
>>>
>>
>> eek. We're in the process of hunting down and eliminating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Wessel wrote:
Andrew Morton wrote:
On Wed, 22 Aug 2007 17:44:12 -0500
Jason Wessel [EMAIL PROTECTED] wrote:
+while (!atomic_read(debugger_active));
eek. We're in the process of hunting down and eliminating exactly this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pete/Piet Delaney wrote:
Jason Wessel wrote:
Andrew Morton wrote:
On Wed, 22 Aug 2007 17:44:12 -0500
Jason Wessel [EMAIL PROTECTED] wrote:
+while (!atomic_read(debugger_active));
eek. We're in the process of hunting down
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pete/Piet Delaney wrote:
Jason Wessel wrote:
Andrew Morton wrote:
On Wed, 22 Aug 2007 17:44:12 -0500
Jason Wessel [EMAIL PROTECTED] wrote:
+while (!atomic_read(debugger_active));
eek. We're in the process of hunting down
can be addressed; for example taking a kernel
core dump after dropping into kgdb and having the registers
show up correctly in Dave Anderson's crash utility.
-piet
>
> -Andi
--
Piet DelaneyPhone: (408) 200-5256
Blue Lane Technologies
dump after dropping into kgdb and having the registers
show up correctly in Dave Anderson's crash utility.
-piet
-Andi
--
Piet DelaneyPhone: (408) 200-5256
Blue Lane Technologies Fax: (408) 200-5299
10450 Bubb Rd.
Cupertino, Ca
On Tue, 2007-04-17 at 11:30 -0700, Randy Dunlap wrote:
> On Thu, 08 Mar 2007 14:24:10 -0800 Piet Delaney wrote:
>
> > On Thu, 2007-03-08 at 11:49 -0700, Tom Rini wrote:
> > > On Thu, Mar 08, 2007 at 07:37:56PM +0100, Andi Kleen wrote:
> > > > On Thursday 08 M
On Tue, 2007-04-17 at 11:30 -0700, Randy Dunlap wrote:
On Thu, 08 Mar 2007 14:24:10 -0800 Piet Delaney wrote:
On Thu, 2007-03-08 at 11:49 -0700, Tom Rini wrote:
On Thu, Mar 08, 2007 at 07:37:56PM +0100, Andi Kleen wrote:
On Thursday 08 March 2007 18:44, Dave Jiang wrote
for Andrew and then the
integration process stopped. I suggest we work together on getting
the kgdb patch back into the mm series and permanently into the kernel
like the kexec code and then we can avoid this kernel development
obfuscation.
-piet
>
--
Piet Delaney
series and permanently into the kernel
like the kexec code and then we can avoid this kernel development
obfuscation.
-piet
--
Piet DelaneyPhone: (408) 200-5256
Blue Lane Technologies Fax: (408) 200-5299
10450 Bubb Rd.
Cupertino, Ca
Christophe Saout wrote:
> Fix corruption issue with dm-crypt on top of software raid5. Cancelled
> readahead bio's that report no error, just have BIO_UPTODATE cleared
> were reported as successful reads to the higher layers (and leaving
> random content in the buffer cache). Already fixed in
ored) root partition. I'm using your patch
that fixes the raid5 problem just to play it safe.
So far it looks like processes are waiting to be woken up by
the buffer cache once reads have completed.
-piet
>
>
> --
> dm-devel mailing list
> [EMAIL PROTECTED]
> https://www.re
like processes are waiting to be woken up by
the buffer cache once reads have completed.
-piet
--
dm-devel mailing list
[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/dm-devel
--
Piet DelaneyPhone: (408) 200-5256
Blue Lane Technologies
Christophe Saout wrote:
Fix corruption issue with dm-crypt on top of software raid5. Cancelled
readahead bio's that report no error, just have BIO_UPTODATE cleared
were reported as successful reads to the higher layers (and leaving
random content in the buffer cache). Already fixed in 2.6.19.
I'm having two unexpected problems with LFS LiveCDs 6.2-3 and 6.2-4
that don't occure on lfslivecd-x86-6.1.1-4.iso. I've got a workaround
for the second problem but haven't found a solution yet for the second;
see 2. below.
1. The first is that I need to add a symbolic pointer from stage
to
I'm having two unexpected problems with LFS LiveCDs 6.2-3 and 6.2-4
that don't occure on lfslivecd-x86-6.1.1-4.iso. I've got a workaround
for the second problem but haven't found a solution yet for the second;
see 2. below.
1. The first is that I need to add a symbolic pointer from stage
to
EAD)
> - && bio_flagged(bio, BIO_UPTODATE)) {
> + if (bio_data_dir(io->bio) == READ && !error) {
> kcryptd_queue_io(io);
> return 0;
> }
>
>
> --
> dm-devel mailing list
> [EMAIL PROTECTED]
>
(io);
return 0;
}
--
dm-devel mailing list
[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/dm-devel
--
Piet DelaneyPhone: (408) 200-5256
Blue Lane Technologies Fax: (408) 200-5299
10450 Bubb Rd
On Wed, 2006-08-30 at 20:00 -0700, Andrew Morton wrote:
> On Wed, 30 Aug 2006 19:42:32 -0700
> Piet Delaney <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 2006-08-30 at 15:57 -0700, Andrew Morton wrote:
> > > On Wed, 30 Aug 2006 14:48:22 -0700
> > >
On Wed, 2006-08-30 at 20:00 -0700, Andrew Morton wrote:
On Wed, 30 Aug 2006 19:42:32 -0700
Piet Delaney [EMAIL PROTECTED] wrote:
On Wed, 2006-08-30 at 15:57 -0700, Andrew Morton wrote:
On Wed, 30 Aug 2006 14:48:22 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Plus: I'd want
22 matches
Mail list logo