vfs: Remove the unnessary check when CONFIG_DEBUG_MM enable
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
This commit is contained in:
parent
f53c776d97
commit
2b0e28e492
@ -720,21 +720,7 @@ static ssize_t fat_write(FAR struct file *filep, FAR const char *buffer,
|
||||
bool force_indirect = false;
|
||||
#endif
|
||||
|
||||
/* Sanity checks. I have seen the following assertion misfire if
|
||||
* CONFIG_DEBUG_MM is enabled while re-directing output to a
|
||||
* file. In this case, the debug output can get generated while
|
||||
* the file is being opened, FAT data structures are being allocated,
|
||||
* and things are generally in a perverse state.
|
||||
*/
|
||||
|
||||
#ifdef CONFIG_DEBUG_MM
|
||||
if (filep->f_priv == NULL || filep->f_inode == NULL)
|
||||
{
|
||||
return -ENXIO;
|
||||
}
|
||||
#else
|
||||
DEBUGASSERT(filep->f_priv != NULL && filep->f_inode != NULL);
|
||||
#endif
|
||||
|
||||
/* Recover our private data from the struct file instance */
|
||||
|
||||
|
@ -490,21 +490,7 @@ static ssize_t hostfs_write(FAR struct file *filep, const char *buffer,
|
||||
FAR struct hostfs_ofile_s *hf;
|
||||
ssize_t ret;
|
||||
|
||||
/* Sanity checks. I have seen the following assertion misfire if
|
||||
* CONFIG_DEBUG_MM is enabled while re-directing output to a
|
||||
* file. In this case, the debug output can get generated while
|
||||
* the file is being opened, FAT data structures are being allocated,
|
||||
* and things are generally in a perverse state.
|
||||
*/
|
||||
|
||||
#ifdef CONFIG_DEBUG_MM
|
||||
if (filep->f_priv == NULL || filep->f_inode == NULL)
|
||||
{
|
||||
return -ENXIO;
|
||||
}
|
||||
#else
|
||||
DEBUGASSERT(filep->f_priv != NULL && filep->f_inode != NULL);
|
||||
#endif
|
||||
|
||||
/* Recover our private data from the struct file instance */
|
||||
|
||||
|
@ -528,21 +528,7 @@ static ssize_t rpmsgfs_write(FAR struct file *filep, const char *buffer,
|
||||
FAR struct rpmsgfs_ofile_s *hf;
|
||||
ssize_t ret;
|
||||
|
||||
/* Sanity checks. I have seen the following assertion misfire if
|
||||
* CONFIG_DEBUG_MM is enabled while re-directing output to a
|
||||
* file. In this case, the debug output can get generated while
|
||||
* the file is being opened, FAT data structures are being allocated,
|
||||
* and things are generally in a perverse state.
|
||||
*/
|
||||
|
||||
#ifdef CONFIG_DEBUG_MM
|
||||
if (filep->f_priv == NULL || filep->f_inode == NULL)
|
||||
{
|
||||
return -ENXIO;
|
||||
}
|
||||
#else
|
||||
DEBUGASSERT(filep->f_priv != NULL && filep->f_inode != NULL);
|
||||
#endif
|
||||
|
||||
/* Recover our private data from the struct file instance */
|
||||
|
||||
|
@ -641,21 +641,7 @@ static ssize_t smartfs_write(FAR struct file *filep, const char *buffer,
|
||||
size_t byteswritten;
|
||||
int ret;
|
||||
|
||||
/* Sanity checks. I have seen the following assertion misfire if
|
||||
* CONFIG_DEBUG_MM is enabled while re-directing output to a
|
||||
* file. In this case, the debug output can get generated while
|
||||
* the file is being opened, FAT data structures are being allocated,
|
||||
* and things are generally in a perverse state.
|
||||
*/
|
||||
|
||||
#ifdef CONFIG_DEBUG_MM
|
||||
if (filep->f_priv == NULL || filep->f_inode == NULL)
|
||||
{
|
||||
return -ENXIO;
|
||||
}
|
||||
#else
|
||||
DEBUGASSERT(filep->f_priv != NULL && filep->f_inode != NULL);
|
||||
#endif
|
||||
|
||||
/* Recover our private data from the struct file instance */
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user