linux-kernel - Re: 2.6.24-rc2-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071114122939.7b4ee194.akpm@linux-foundation.org>
Date:	Wed, 14 Nov 2007 12:29:39 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Torsten Kaiser" <just.for.lkml@...glemail.com>
Cc:	linux-kernel@...r.kernel.org,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Trond Myklebust <trond.myklebust@....uio.no>
Subject: Re: 2.6.24-rc2-mm1

On Wed, 14 Nov 2007 20:16:09 +0100 "Torsten Kaiser" <just.for.lkml@...glemail.com> wrote:

> On Nov 14, 2007 2:59 AM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc2/2.6.24-rc2-mm1/
> 
> Breaks nfsv4 in a rather funny way:
> 
> treogen ~ # cd /usr/portage/x
> treogen x # touch bla
> touch: cannot touch `bla': File exists
> treogen x # mkdir bla
> treogen x # touch bla/bla
> touch: cannot touch `bla/bla': File exists
> treogen x # ls -lad *
> drwxr-xr-x 2 root root 6 Nov 14 20:03 bla
> treogen x # ls -la *
> total 0
> drwxr-xr-x 2 root root  6 Nov 14 20:03 .
> drwxr-xr-x 3 root root 16 Nov 14 20:03 ..
> treogen x #
> 
> So I can create new directories, but not new files. Reading files works normal.
>>
> The client is 2.6.24-rc2-mm1, the server 2.6.22-gentoo-r9.
> The fstab-line from the client:
> 192.168.2.4:/portage    /usr/portage            nfs4
> rw,noatime,nodiratime,intr 0 0
> 
> 2.6.23-mm1 as client worked, some 2.6.24-rc1-git? also.

hm.  I guess that means I get to do yet another git-bisect.  Either the nfs
changes or r-o-bind-mounts, I bet.

> Otherwise the new -mm worked OK for me, no errors visible in the syslog.
> It even fixed the ACPI Exception from regression bug 9320.
> Now the output is:
> [   83.125873] scsi8 : pata_amd
> [   83.125917] scsi9 : pata_amd
> [   83.127062] ata9: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
> [   83.127064] ata10: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
> [   83.194917] ata9.01: ATA-7: Maxtor 6L250R0, BAH41G10, max UDMA/133
> [   83.194920] ata9.01: 490234752 sectors, multi 16: LBA48
> [   83.194929] ata9: nv_mode_filter: 0x7f39f&0x701f->0x701f,
> BIOS=0x7000 (0xc00000) ACPI=0x701f (900:60:0x14)
> [   83.197327] ata9.01: configured for UDMA/33
> [   83.197348] ata10: port disabled. ignoring.
> [   83.197428] scsi 8:0:1:0: Direct-Access     ATA      Maxtor 6L250R0
>   BAH4 PQ: 0 ANSI: 5
> [   83.197487] sd 8:0:1:0: [sdd] 490234752 512-byte hardware sectors (251000 MB)
> [   83.197496] sd 8:0:1:0: [sdd] Write Protect is off
> [   83.197498] sd 8:0:1:0: [sdd] Mode Sense: 00 3a 00 00
> [   83.197510] sd 8:0:1:0: [sdd] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [   83.197542] sd 8:0:1:0: [sdd] 490234752 512-byte hardware sectors (251000 MB)
> [   83.197549] sd 8:0:1:0: [sdd] Write Protect is off
> [   83.197551] sd 8:0:1:0: [sdd] Mode Sense: 00 3a 00 00
> [   83.197562] sd 8:0:1:0: [sdd] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [   83.197565]  sdd: sdd1 sdd2 sdd3 sdd4 < sdd5 sdd6 >
> [   83.222911] sd 8:0:1:0: [sdd] Attached SCSI disk
> [   83.222944] sd 8:0:1:0: Attached scsi generic sg3 type 0
> 
> Just posting this, if someone is interested in the nv_mode_filter-output...
> (UDMA/33 is correct, its only a 40-wire cable)
> 

OK, thanks.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/