linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Amir Goldstein <amir73il@gmail.com>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: fix NULL pointer dereference in ext4_quota_off
Date: Mon, 16 May 2011 10:04:35 -0400	[thread overview]
Message-ID: <20110516140435.GA4953@thunk.org> (raw)
In-Reply-To: <20110516101154.GB5344@quack.suse.cz>

On Mon, May 16, 2011 at 12:11:54PM +0200, Jan Kara wrote:
>   Ah, I see we worked on the patch together :). Anyway, Ted can pick any of
> them I guess.

I actually combined the commit description and used elements from both
of them.  Jan's short description was a better summary, but I liked
Amir description of the commit (note though that if you're going to
use abberviated git commit id's, please don't shorten them to 10-12
characters since given the size of the git repository, shorter git
commit id's could suffer from hash collision).

						- Ted

ext4: fix oops in ext4_quota_off()

From: Amir Goldstein <amir73il@gmail.com>

If quota is not enabled when ext4_quota_off() is called, we must not
dereference quota file inode since it is NULL.  Check properly for
this.

This fixes a bug in commit 21f976975cbe (ext4: remove unnecessary
[cm]time update of quota file), which was merged for 2.6.39-rc3.

Reported-by: Amir Goldstein <amir73il@users.sf.net>
Signed-off-by: Amir Goldstein <amir73il@users.sf.net>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

						- Ted

  reply	other threads:[~2011-05-16 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16  9:31 [PATCH] ext4: fix NULL pointer dereference in ext4_quota_off Amir Goldstein
2011-05-16  9:49 ` Lukas Czerner
2011-05-16 10:13   ` Jan Kara
2011-05-16 10:53     ` Lukas Czerner
2011-05-16 11:03       ` Jan Kara
2011-05-16 10:11 ` Jan Kara
2011-05-16 14:04   ` Ted Ts'o [this message]
2011-05-16 14:40     ` Amir Goldstein

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=20110516140435.GA4953@thunk.org \
    --to=tytso@mit.edu \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    /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).