linux-kernel - Re: kernel BUG at fs/inode.c

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <200711221820.lAMIKFkQ005124@cfif3.ist.utl.pt>
Date:	Thu, 22 Nov 2007 18:20:15 +0000 (WET)
From:	paulo@...f3.ist.utl.pt
To:	jack@...e.cz
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kernel BUG at fs/inode.c

  Hi,

>  Thanks for report. It looks like a problem in UDF. Actually I think
> I've already seen a similar report. Are there any IO errors in the logs
> or anything else suspitious?

 At the risk of reporting further bugs :-) here it goes:

=======================================================================

 1)

 Something I've recently reported to the e-mail address listed
 on the mkudffs manpage:

 ...a small problem with mkudffs, as obtained from
 udftools-1.0.0b3-7.fc6.

 The problem is as follows: if I take a new DVD-RAM, create (say)
 an ext3 filesystem, and some time later I run mkudffs over it,
 then when I try to mount it the disk still seems to remember
 about having had a previous filesystem.
 What I mean is that mount may succeed if one specifies the newer
 filesystem, at least if no files have been copied yet, and also
 succeed with the older filesystem.

 Here is an example, for the same disk(!) without any formatting
 nor copying in between (note also the dates)

# mount /dev/scd0 /mnt/dvd -t udf
# ll /mnt/dvd/
total 4
drwxr-xr-x  3 root root   92 2007-11-21 18:34 ./
drwxr-xr-x 13 root root 4096 2007-09-03 17:27 ../
drwxr-xr-x  2 root root   40 2007-11-21 18:34 lost+found/

# umount /mnt/dvd
# mount /dev/scd0 /mnt/dvd -t ext3
# ll /mnt/dvd/
total 24
drwxr-xr-x  3 root root  4096 2007-11-21 19:29 ./
drwxr-xr-x 13 root root  4096 2007-09-03 17:27 ../
drwx------  2 root root 16384 2007-11-21 19:29 lost+found/

 Eventually I found that I could erase the (or at least part of the)
 information that remained from ext3 by using fdisk to set a filesystem
 of type "0" ("empty") and then running mkudffs over.

 That is not very practical of course, and I am also not completely
 sure that no other outdated info remains on the disk.

=======================================================================

 2)

 With 2.6.24-rc1-git10 (did not see it with other kernels yet)

 # find /proc -name cdrom
 /proc/sys/dev/cdrom
 find: WARNING: Hard link count is wrong for /proc/net: this may be
 a bug in your filesystem driver.  Automatically turning on find's
 -noleaf option.  Earlier results may have failed to include
 directories that should have been searched.

=======================================================================

 3)

 While I am at it, here's a suggestion. One of my DVD-RAM disks
 had apparently some (likely minor) problems, because I've just
 found the following notice in /var/log/messages :

 ... kernel: EXT3-fs warning: mounting fs with errors, running
 e2fsck is recommended

 This message appears 11 times in that file. I've never seen it
 displayed on an xterm, although I always mount the disks "by hand",
 on the command line!

 The request/suggestion is (obviously) please send that message to
 syserror too!!

=======================================================================

 Which other logs should I look at?

  Best regards
   Paulo

-
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/