From: Ted Ts'o <tytso@mit.edu>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
Jan Kara <jack@suse.cz>, Eric Sandeen <sandeen@redhat.com>,
Christoph Hellwig <hch@lst.de>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NULL pointer dereference in print_daily_error_info
Date: Tue, 14 Sep 2010 15:46:41 -0400 [thread overview]
Message-ID: <20100914194641.GB3730@thunk.org> (raw)
In-Reply-To: <20100914125102.GA5318@swordfish.minsk.epam.com>
On Tue, Sep 14, 2010 at 03:51:02PM +0300, Sergey Senozhatsky wrote:
> Hello,
>
> This patch fixes NULL pointer dereference in print_daily_error_info, when
> called
> on unmounted fs (EXT4_SB(sb) returns NULL). Deleting error reporting timer
> in
> ext4_put_super fixes oops.
Good catch! Thanks for the patch. I will include this into ext4
tree, and I will probably push it separately to Linus so that it gets
into 2.6.36, since this is a regresssion.
You didn't add a Signed-off-by: line, which is needed for Developer's
Certification of Origin (see section 1, subsection 16 of
Documentation/SubmittingPatches in the Linux source tree). Can you
send confirmation that it's OK for me to add a Signed-off-by line for
you? Thanks!!
> By the way, isn't print_daily_error_info racy? Is it safe to call
> print_daily_error_info
> (by timer event (softirq)) when we'are remounting fs, etc.?
It should be fine. Remounting doesn't actually change out the struct
superblock. There is a chance that the information might not be fully
complete if an error is printed exactly as the same time as
print_daily_error_info() is run, but I'm not sure it's worth trying to
protect against that race, since the worst that this will mean is a
confusing report in the /var/log/messages file, and the ext4 error
message will be printed right next to it, which will have all of the
information the system administrator will need.
- Ted
next prev parent reply other threads:[~2010-09-14 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 12:51 NULL pointer dereference in print_daily_error_info Sergey Senozhatsky
2010-09-14 19:46 ` Ted Ts'o [this message]
2010-09-15 6:35 ` [PATCH] ext4: fix " Sergey Senozhatsky
2010-09-15 6:35 ` Sergey Senozhatsky
2010-09-20 14:21 ` Ted Ts'o
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=20100914194641.GB3730@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sergey.senozhatsky@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 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.