From: Anton Altaparmakov <aia21@cus.cam.ac.uk>
To: preining@logic.at
Cc: linux-kernel@vger.kernel.org, andre@linuxdiskcert.org
Subject: Re: [BUG] 2.4.18.3, ide-patch, read_dev_sector hangs in read_cache_page
Date: Tue, 15 Jan 2002 13:54:57 +0000 (GMT) [thread overview]
Message-ID: <E16QU3F-0005g6-00@libra.cus.cam.ac.uk> (raw)
Hi Norbert,
Could you try this patchlet to fs/partitions/check.c::read_dev_sector() and look if there is any output by dmesg? It's
a bit of a shot in the dark but will at least exclude this as the source for the peoblem...
diff -u -ur linux-2.4.18-pre3-ac2/fs/partitions/check.c linux-2.4.18-pre3-ac2-aia1/fs/partitions/check.c
--- linux-2.4.18-pre3-ac2/fs/partitions/check.c Fri Oct 12 01:25:10 2001
+++ linux-2.4.18-pre3-ac2-aia1/fs/partitions/check.c Tue Jan 15 13:21:24 2002
@@ -410,6 +410,14 @@
int sect = PAGE_CACHE_SIZE / 512;
struct page *page;
+ if (mapping->a_ops->sync_page != block_sync_page) {
+ if (mapping->a_ops->sync_page)
+ printk(KERN_CRIT "read_dev_sector: mapping->a_ops->sync_page != block_sync_page!\n");
+ else {
+ printk(KERN_CRIT "read_dev_sector: mapping->a_ops->sync_page is NULL! Setting to default block_sync_page!\n");
+ mapping->a_ops->sync_page = block_sync_page;
+ }
+ }
page = read_cache_page(mapping, n/sect,
(filler_t *)mapping->a_ops->readpage, NULL);
if (!IS_ERR(page)) {
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next reply other threads:[~2002-01-15 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 13:54 Anton Altaparmakov [this message]
2002-01-15 15:03 ` [BUG] 2.4.18.3, ide-patch, read_dev_sector hangs in read_cache_page Norbert Preining
[not found] ` <20020116094935.A20738@alpha.logic.tuwien.ac.at>
2002-01-16 9:27 ` Norbert Preining
2002-01-16 9:50 ` Anton Altaparmakov
2002-01-16 11:27 ` Norbert Preining
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 12:29 Norbert Preining
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16QU3F-0005g6-00@libra.cus.cam.ac.uk \
--to=aia21@cus.cam.ac.uk \
--cc=andre@linuxdiskcert.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.