mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Enze Li <lienze@kylinos.cn>, Phillip Potter <phil@philpotter.co.uk>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] cdrom: do not print info list when there is no cdrom device
Date: Mon, 11 Apr 2022 10:51:28 -0600	[thread overview]
Message-ID: <226c4072-a3ca-a5a4-1b7f-f7104b43af03@kernel.dk> (raw)
In-Reply-To: <f74b6933-5357-6b2c-3127-7a3465dadbdf@kylinos.cn>

On 4/11/22 2:41 AM, Enze Li wrote:
> 
> On 4/9/22 16:16, Phillip Potter wrote:
>> On Sat, Apr 09, 2022 at 12:25:30PM +0800, Enze Li wrote:
> 
> <snip>
> 
>>> On Fri, 8 Apr 2022 06:34:04 -0600
>>> Jens Axboe <axboe@kernel.dk> wrote:
>>>> Will this potentially break applications that parse it?
>>>>
>>> I dunno, is there any way to confirm this thing?  And if this is really
>>> a possibility, does it mean that we cannot make changes?
>>>
>> Sorry, anything that can be parsed from userspace has the potential to
>> break userspace applications. For that reason, I would have to say I
>> don't think this patch is suitable. Sure there are times it's
>> appropriate to change userspace interfaces, but I'd rather err on the
>> side of caution here. Thanks for the patch though.
>>
>> Nacked-by: Phillip Potter <phil@philpotter.co.uk>
>>
>> Regards,
>> Phil
> 
> Hi Phil,
> 
> Thanks for your review.  I got what you said. ?
> 
> In addition, I noticed that in the source file[1], there is a Todo List there.  I'm quite
> interested in it.  It says:
> ================================================
>   17 To Do List:
>   18 ----------------------------------
>   19
>   20  -- Modify sysctl/proc interface. I plan on having one directory per                 
>   21  drive, with entries for outputing general drive information, and sysctl             
>   22  based tunable parameters such as whether the tray should auto-close for             
>   23  that drive. Suggestions (or patches) for this welcome!
> ================================================
> I'd like to know if the relevant patches are still welcome?
> 
> IIUC, the TODO List says that we need to implement a modification of the
> following form:
> ----------------------------------------------------------------------------------------------------------
> $ tree /proc/sys/dev/cdrom
> /proc/sys/dev/cdrom
> |--sr0--autoclose
> |       |-autoeject
> |       |-check_media
> |       |-debug
> |       |-info
> |       |-lock
> |
> |--sr1--autoclose
> |       |-autoeject
> |       |-check_media
> |       |-debug
> |       |-info
> |       |-lock
> |
> |--sr2 ...
> .
> .
> .
> ----------------------------------------------------------------------------------------------------------
> I would appreciate it if you could give me some advice.

Let's not do that, this advice is perhaps 20 years old. /proc isn't to
be used for anything like that these days.

-- 
Jens Axboe


  parent reply	other threads:[~2022-04-11 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  8:42 Enze Li
2022-04-08 12:34 ` Jens Axboe
2022-04-09  4:25   ` Enze Li
2022-04-09  8:16     ` Phillip Potter
     [not found]       ` <f74b6933-5357-6b2c-3127-7a3465dadbdf@kylinos.cn>
2022-04-11 16:51         ` Jens Axboe [this message]
2022-04-18 21:04           ` Phillip Potter

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=226c4072-a3ca-a5a4-1b7f-f7104b43af03@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=lienze@kylinos.cn \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil@philpotter.co.uk \
    /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®