This is a note to let you know that I've just added the patch titled

    pstore: Fail to unlink if a driver has not defined

to the 3.10-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     pstore-fail-to-unlink-if-a-driver-has-not-defined.patch
and it can be found in the queue-3.10 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From bf2883339a33b7544b92ea465b90c3de55082032 Mon Sep 17 00:00:00 2001
From: Aruna Balakrishnaiah <[email protected]>
Date: Tue, 25 Jun 2013 14:33:56 +0530
Subject: pstore: Fail to unlink if a driver has not defined
 pstore_erase

From: Aruna Balakrishnaiah <[email protected]>

commit bf2883339a33b7544b92ea465b90c3de55082032 upstream.

pstore_erase is used to erase the record from the persistent store.
So if a driver has not defined pstore_erase callback return
-EPERM instead of unlinking a file as deleting the file without
erasing its record in persistent store will give a wrong impression
to customers.

Signed-off-by: Aruna Balakrishnaiah <[email protected]>
Acked-by: Kees Cook <[email protected]>
Signed-off-by: Tony Luck <[email protected]>
Cc: HuKeping <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/pstore/inode.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/fs/pstore/inode.c
+++ b/fs/pstore/inode.c
@@ -178,6 +178,8 @@ static int pstore_unlink(struct inode *d
        if (p->psi->erase)
                p->psi->erase(p->type, p->id, p->count,
                              dentry->d_inode->i_ctime, p->psi);
+       else
+               return -EPERM;
 
        return simple_unlink(dir, dentry);
 }


Patches currently in stable-queue which might be from [email protected] 
are

queue-3.10/pstore-fail-to-unlink-if-a-driver-has-not-defined.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to