Hi.
Sorry.
It's not really a bug in the swapoff code. Rather, clearing this field
allows simple identification of the devices being used for swap (for
flushing writes).
Regards,
Nigel
On Wed, 2005-07-06 at 18:15, Pavel Machek wrote:
> On St 06-07-05 12:20:40, Nigel Cunningham wrote:
> > diff -ruNp 405-clear-swapfile-bdev-in-swapoff.patch-old/mm/swapfile.c 405-clear-swapfile-bdev-in-swapoff.patch-new/mm/swapfile.c
> > --- 405-clear-swapfile-bdev-in-swapoff.patch-old/mm/swapfile.c 2005-07-06 11:22:01.000000000 +1000
> > +++ 405-clear-swapfile-bdev-in-swapoff.patch-new/mm/swapfile.c 2005-07-04 23:14:19.000000000 +1000
> > @@ -1162,6 +1162,7 @@ asmlinkage long sys_swapoff(const char _
> > swap_file = p->swap_file;
> > p->swap_file = NULL;
> > p->max = 0;
> > + p->bdev = NULL;
> > swap_map = p->swap_map;
> > p->swap_map = NULL;
> > p->flags = 0;
>
> I guess some explanation is needed here; and if it is bugfix it should
> just go in...
> Pavel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |