From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Willy Tarreau <willy@w.ods.org>
Cc: Greg K-H <greg@kroah.com>, linux-kernel@vger.kernel.org, sct@redhat.com
Subject: Re: [PATCH] Fix root hole in raw device
Date: Tue, 17 May 2005 08:38:27 +0100 [thread overview]
Message-ID: <20050517073827.GS1150@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050517070735.GB31163@alpha.home.local>
On Tue, May 17, 2005 at 09:07:35AM +0200, Willy Tarreau wrote:
> > struct block_device *bdev = filp->private_data;
> > int err = -EINVAL;
> >
> > - return ioctl_by_bdev(bdev, command, arg);
> > + if (bdev && bdev->bd_inode)
> > + err = blkdev_ioctl(bdev->bd_inode, filp, command, arg);
> ^^^^^^^
> Sorry, I forgot it...
> I meant the same with the NULL. Is it OK ?
What is that if () doing there? bdev->bd_inode is *never* NULL - it's
set when we allocate the bdev and never changed; the code setting it
is
if (inode->i_state & I_NEW) {
bdev->bd_contains = NULL;
bdev->bd_inode = inode;
so you are not going to have it NULL, no matter what.
And filp->private_data is set in raw_open() by
filp->private_data = bdev;
a couple of lines after
filp->f_mapping = bdev->bd_inode->i_mapping;
so it's not going to be NULL either.
next prev parent reply other threads:[~2005-05-17 7:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 4:37 [GIT PATCH] Stable bugfixes for 2.6.12-rc4 Greg KH
2005-05-17 4:37 ` [PATCH] fix Linux kernel ELF core dump privilege elevation Greg KH
2005-05-17 4:37 ` [PATCH] Fix root hole in raw device Greg KH
2005-05-17 4:37 ` [PATCH] Fix root hole in pktcdvd Greg KH
2005-05-17 5:00 ` Al Viro
2005-05-17 5:54 ` Al Viro
2005-05-17 18:12 ` Peter Osterlund
2005-05-17 15:35 ` Greg KH
2005-05-17 4:57 ` [PATCH] Fix root hole in raw device Al Viro
2005-05-17 7:03 ` Willy Tarreau
2005-05-17 7:07 ` Willy Tarreau
2005-05-17 7:38 ` Al Viro [this message]
2005-05-17 7:32 ` Al Viro
2005-05-17 13:04 ` Stephen C. Tweedie
2005-05-17 16:53 ` Al Viro
2005-05-22 11:55 ` Peter Osterlund
2005-05-22 11:57 ` Peter Osterlund
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=20050517073827.GS1150@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=willy@w.ods.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
Powered by JetHome