linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	saeed bishara <saeed.bishara@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	DE/ATA development list <linux-ide@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>,
	Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Subject: Re: [BUG] bug when enabling VM DEBUG
Date: Wed, 12 May 2010 13:53:40 +0200	[thread overview]
Message-ID: <20100512115340.GA11261@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <1273662639.23818.67.camel@e102109-lin.cambridge.arm.com>

* Catalin Marinas | 2010-05-12 12:10:39 [+0100]:

>> > --- a/drivers/ata/libata-sff.c
>> > +++ b/drivers/ata/libata-sff.c
>> > @@ -894,7 +894,7 @@ static void ata_pio_sector(struct ata_queued_cmd *qc)
>> >                                         do_write);
>> >          }
>> >
>> > -       if (!do_write)
>> > +       if (!do_write&&  !PageSlab(page))
>> >                  flush_dcache_page(page);
>> 
>> I would think that check belongs inside flush_dcache_page itself, rather
>> than forcing every driver to include it..
>
>Sebastian (cc'ed) reported this as well for MIPS.
Thx. The patch above looks what I've sent a while ago. Jeff was going to
merge it afaik.

>I think it makes sense for this check to be done in the
>flush_dcache_page() function.

Why should flush_dcache_page() not flush pages you tell it?
>From Documentation/cachetlb.txt:
|   NOTE: This routine need only be called for page cache pages
|          which can potentially ever be mapped into the address
|          space of a user process.  So for example, VFS layer code
|          handling vfs symlinks in the page cache need not call
|          this interface at all.

A page from slab or stack is not going to see the sky of user land and
therefore it should not be fed into flush_dcache_page().

Sebastian

  reply	other threads:[~2010-05-12 11:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 13:06 [BUG] bug when enabling VM DEBUG saeed bishara
2010-05-10 13:09 ` saeed bishara
2010-05-11 15:27 ` saeed bishara
2010-05-12  2:41   ` Robert Hancock
2010-05-12 11:10     ` Catalin Marinas
2010-05-12 11:53       ` Sebastian Andrzej Siewior [this message]
2010-05-12 12:24         ` Catalin Marinas
2010-05-12 13:06           ` Jamie Lokier
2010-05-12 23:22             ` Robert Hancock
2010-05-13 11:30             ` Catalin Marinas
2010-05-14 21:48               ` Jeff Garzik

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=20100512115340.GA11261@Chamillionaire.breakpoint.cc \
    --to=sebastian@breakpoint.cc \
    --cc=catalin.marinas@arm.com \
    --cc=hancockrwd@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saeed.bishara@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).