mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Gabriel C <nix.or.die@googlemail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc2-mm1
Date: Wed, 18 Oct 2006 15:46:36 -0700	[thread overview]
Message-ID: <20061018154636.2317059a.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0610190031260.29022@twin.jikos.cz>

On Thu, 19 Oct 2006 00:41:40 +0200 (CEST)
Jiri Kosina <jikos@jikos.cz> wrote:

> On Wed, 18 Oct 2006, Andrew Morton wrote:
> 
> > > The inode->i_mutex should be held every time when calling 
> > > i_size_write(), and the function contains WARN_ON() for that 
> > > condition. page_symlink(), however, does not lock i_mutex. It is 
> > > perfectly OK, as the i_mutex for the directory is held at the time 
> > > page_symlink() is running, so noone is able to change i_size during 
> > > race condition. However, i_size_write() spits out the warning without 
> > > this patch.
> > I suspect it isn't necessary because the symlink's inode hasn't been wired
> > up into the directory tree yet and no other thread can find it and do
> > things to it.
> 
> I completely agree (see my comments to the patch in previous mail). 
> However, the warning emitted by i_size_write() should really go away. I 
> can see the following possibilities:
> 
> - lock the i_mutex, even though it's for sure not necessary. Not nice.
> - remove the warning from i_size_write(). Not nice either, we want to be 
> warned about other calls that are not correct
> - make the warning in i_size_write() conditional on inode->i_dentry not 
> being NULL (?)
> 

I simply dropped the debugging patch.  Which is pretty sad, because it _is_ a
really nasty and subtle-to-show bug.  So I'd be OK with adding sufficient
patches to -mm to make the false positives go away so we can re-add the
check.


  reply	other threads:[~2006-10-18 22:46 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17  6:06 2.6.19-rc2-mm1 Andrew Morton
     [not found] ` <a44ae5cd0610170003r77595cc0p8ed66badde952859@mail.gmail.com>
2006-10-17  7:36   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-17  8:41 ` 2.6.19-rc2-mm1 Brice Goglin
2006-10-17 12:54   ` [PATCH] backlight users need to select BACKLIGHT_CLASS_DEVICE Andy Whitcroft
2006-10-17 13:17 ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-17 14:23 ` 2.6.19-rc2-mm1 Andy Whitcroft
2006-10-17 16:07   ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-17 18:22   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:44   ` 2.6.19-rc2-mm1 Dylan Taft
2006-10-17 15:45 ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-17 18:29   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-20 13:40     ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-17 19:37 ` 2.6.19-rc2-mm1 Jeremy Fitzhardinge
2006-10-17 20:22   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 10:05     ` 2.6.19-rc2-mm1 Michael Ellerman
2006-10-18 19:05       ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-17 19:53 ` [2.6.19-rc2-mm1] error: too few arguments to function ‘crypto_alloc_hash’ Andrew James Wade
2006-10-17 21:19   ` Edward Shishkin
2006-10-18 16:53     ` Andrew James Wade
2006-10-18 15:33 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 15:48   ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:15     ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 17:26       ` 2.6.19-rc2-mm1 Chris Mason
2006-10-18 17:32       ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:41         ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 17:56           ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:58         ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 18:14           ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 18:22             ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 18:31             ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 23:59               ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 22:44           ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 23:01             ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 23:25               ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19  0:07                 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-19  0:21                   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 15:28                     ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-19 12:32                 ` 2.6.19-rc2-mm1 Andi Kleen
2006-10-19 16:18                   ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 16:57                     ` 2.6.19-rc2-mm1 Andi Kleen
2006-10-18 18:27 ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 19:18   ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-18 19:33     ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-18 19:42       ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 20:20         ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-18 20:26         ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-18 22:23           ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 16:05             ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-19 18:10               ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-20  7:37                 ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-18 20:22       ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 18:42 ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 21:44   ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 22:29     ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:41       ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 22:46         ` Andrew Morton [this message]
2006-10-18 22:57           ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 23:04             ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 23:12               ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 14:45 ` 2.6.19-rc2-mm1 // errors in verify_redzone_free() Mariusz Kozlowski
2006-10-19 17:03   ` Andrew Morton
2006-10-19 17:17     ` Jean Tourrilhes
2006-10-19 17:25       ` Andrew Morton
2006-10-19 17:47         ` Jean Tourrilhes
2006-10-19 18:31           ` Mariusz Kozlowski
2006-10-19 18:33             ` Jean Tourrilhes
2006-10-19 17:33       ` Mariusz Kozlowski

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=20061018154636.2317059a.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@googlemail.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

all inboxes | Powered by JetHome®