From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org, tpepper@vato.org
Subject: Re: b_dev vs. b_rdev confusion
Date: Tue, 19 Jun 2001 20:55:44 +0200 (MET DST) [thread overview]
Message-ID: <UTC200106191855.UAA310765.aeb@vlet.cwi.nl> (raw)
> how do the inode->i_dev, i_rdev fit into this?
These are what you see with stat(2).
i_dev gives the device the file is on
i_rdev is usually undefined, but for device special files
it gives the real device.
> Is there a set rule on when/where one should use a buffer head's
> b_dev and when/where one should use b_rdev?
b_dev gives the device the user was thinking about
b_rdev is the actual underlying device
Andries
next reply other threads:[~2001-06-19 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 18:55 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-19 18:11 tpepper
2001-06-19 18:25 ` Tim Pepper
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=UTC200106191855.UAA310765.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tpepper@vato.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
all inboxes | Powered by JetHome®