Paulo da Silva escreveu:
> Paulo da Silva escreveu:
>
> I further simplified this ...
> Now, everything I have is reading a page after sector 1 (sector 0 also
> fails).
> Why does err come with -5?
> What am I doing wrong?
>
> ...
> bio->bi_rw=0;
> c
Paulo da Silva escreveu:
I further simplified this ...
Now, everything I have is reading a page after sector 1 (sector 0 also
fails).
Why does err come with -5?
What am I doing wrong?
/*
* ptm_bio01.c
*Using bio:
*Read data.
*/
#include/* Needed by all modules */
#include
Hi!
I am writing a very trivial module.
It uses submit_bio to write a page to a device and then read it back.
It works but submit_bio returns -5 error code when reading. Neverthless
the data is correctly read! The uptodate bit of bi_flags also does not
get set!
I am using k 2.26.29 on UML x86_64.
Hi!
After some badblocks problems on my sdb drive, I did a reboot.
My system has 2 SATA HDs (sda and sdb), but now the HDs are identified
as sda and sdc!
Log files show that something (kernel?) is trying to access a non
existant sdb and after several unsuccessful accesses (the disk does not
exist)
Hi!
Do I need to use kmap() to get the address of a page I got using for
example find_get_page, or page_address() is enough?
What, in this context, does kmap_atomic()?
Thanks
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read th
Paulo da Silva escreveu:
rishi agrawal escreveu:
You can pick the whole dir of ext2, rename it to another name foo. Then
change all occurences of ext2 to foo, EXT2 to FOO, Ext2 to Foo (this
one not sure if it exists) and you have a new filesystem foo. You may
need to change back some FOO or
rishi agrawal escreveu:
You can pick the whole dir of ext2, rename it to another name foo. Then
change all occurences of ext2 to foo, EXT2 to FOO, Ext2 to Foo (this
one not sure if it exists) and you have a new filesystem foo. You may
need to change back some FOO or foo to EXT2 or ext2 because t
Peter Teoh escreveu:
On Thu, Sep 11, 2008 at 8:48 PM, Paulo da Silva <[EMAIL PROTECTED]> wrote:
...
Second concept is that this bd_inode is to create the object in the
buffer cache to buffer the data for the physical device - this is
where address space mapping comes in.
To answe
Suppose the following situation:
1. Lock a cached page
2. Change it
3. Set it dirty
4. Unlock the page
From this point, it is assumed that the kernel may write the page.
How can I prevent the page from being written, even if some "sync"
function is called like, for example, filemap_write_and_wai
Peter Teoh escreveu:
On Thu, Sep 11, 2008 at 8:48 PM, Paulo da Silva <[EMAIL PROTECTED]> wrote:
...
Second concept is that this bd_inode is to create the object in the
buffer cache to buffer the data for the physical device - this is
where address space mapping comes in.
To answe
Peter Teoh escreveu:
I don't really understand the meaning of "will die".
So don't I.
...
so when bd_inode "will die", does it mean that the inode will become
non-available?
Well ... I thought the element "bd_inode" will be removed from the
device structure. But it is heavily used! "mappin
I am having problems posting to this list. So I am performing some tests
to try to diagnose the problem to report to my ISP. Sorry for the
inconvenience.
Paulo
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://k
):
struct block_device *bdev=open_bdev_excl("", ...);
struct address_space *mapping=bdev->bd_inode->i_mapping;
If bd_inode "will die", how do I do?
On Tue, Sep 9, 2008 at 11:46 AM, Paulo da Silva <[EMAIL PROTECTED]> wrote:
In kernel 2.6.25, bd_inode of struct block_dev
Paulo da Silva escreveu:
Sorry for the multiple post, but this was caused by a problem in my ISP
server.
Thanks.
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://kernelnewbies.org/FAQ
In kernel 2.6.25, bd_inode of struct block_device has the comment "/*
will die */".
How can I get the address space (mapping) of a block device without
using bd_inode?
Thanks
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the
In kernel 2.6.25, bd_inode of struct block_device has the comment "/*
will die */".
How can I get the address space (mapping) of a block device without
using bd_inode?
Thanks
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the
In kernel 2.6.25, bd_inode of struct block_device has the comment "/*
will die */".
How can I get the address space (mapping) of a block device without
using bd_inode?
Thanks
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the
Thomas Petazzoni escreveu:
...
Paulo was
probably referring to I/O barriers, as described in
Documentation/block/barrier.txt.
Yes, that's the point ...
However, I'm not sure I understand Paulo's request properly. Issuing an
I/O barrier is simply a matter of issuing a bio structure with the
Balraj Dahiya escreveu:
Hi All,
I started reading kernel source code.I have confusion about bitwise
operation,left and right shift operation working in Linux Kernel.Can
anybody tell me how these operations works in Linux Kernel?
If I understood your question, this is a C question and no
Thomas Petazzoni escreveu:
...
Paulo was
probably referring to I/O barriers, as described in
Documentation/block/barrier.txt.
Yes, that's the point ...
However, I'm not sure I understand Paulo's request properly. Issuing an
I/O barrier is simply a matter of issuing a bio structure with the
Hi!
I am learning linkux kernel internals and facing the following problem:
1. I use __bread to read a fixed place block on a block drive.
2. I use submit_bio to read/write data on the same drive. The order the
data is written may be arbitrary and, in general, it almost never occur
at the sam
21 matches
Mail list logo
