From: " José Luis Alarcón Sánchez" <jlas9@lycos.es>
To: undisclosed-recipients:;
Subject: Re: [PATCH] remove superfluous inode superblock check from shmem_mmap
Date: Sun, 15 Jun 2003 18:40:21 +0100 [thread overview]
Message-ID: <1055695221031088@lycos-europe.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
>
> ------- Mensaje Original -------
>
> DeJames Morris <jmorris@intercode.com.au>
> FechaMon, 16 Jun 2003 02:14:37 +1000 (EST)
>
>This patch against current 2.5 bk removes a (now) unecessary check
for an
>inode superblock in shmem_mmap(). In the current kernel, all inodes
must
>be associated with a superblock.
>
>- James
>--
>James Morris
>
>
>diff -purN -X dontdiff bk.pending/mm/shmem.c bk.w1/mm/shmem.c
>--- bk.pending/mm/shmem.c 2003-06-16 00:56:13.000000000 +1000
>+++ bk.w1/mm/shmem.c 2003-06-16 02:06:55.142303751 +1000
>@@ -1010,7 +1010,7 @@ static int shmem_mmap(struct file *file,
> struct inode *inode = file->f_dentry->d_inode;
>
> ops = &shmem_vm_ops;
>- if (!inode->i_sb || !S_ISREG(inode->i_mode))
>+ if (!S_ISREG(inode->i_mode))
> return -EACCES;
> update_atime(inode);
> vma->vm_ops = ops;
>
Can i apply this patch against the 2.5.69 kernel?.
Thanks yo very much, in advance.
Regards.
Jose.
http://linuxespana.scripterz.org
FreeBSD RELEASE 4.8.
Mandrake Linux 9.1 Kernels 2.4.21 & 2.5.69 XFS.
Registered Linux User #213309.
Memories..... You are talking about memories.
Rick Deckard. Blade Runner.
_________________________________________________________
Envia tus postales desde Tarjetas Nico. Entra en http://www.tarjetasnico.com/es/index.html?partner=lycoses&nico_usr=premium
next reply other threads:[~2003-06-15 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 17:40 José Luis Alarcón Sánchez [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-15 16:14 James Morris
2003-06-15 17:44 ` Hugh Dickins
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=1055695221031088@lycos-europe.com \
--to=jlas9@lycos.es \
/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®